Question: what is the appropriate way to store config information

[swright-eti]

I have an app that I will be deploying to multiple environments. What is the best way to store config information like hostnames, etc.? I see that I could use Temporary State, but that seems a little clunky. am I missing something?

P.S. this is a fantastic tool.

[neon-balcony]

Hi @swright-eti,

Thanks for the post, just to make sure we're on the same page, could you please elaborate your scenario on "config information like hostnames, etc." and its relationship with "multiple environments"?

[swright-eti]

When the app is running on environment A then the URLs for the REST API calls need to use hostname X
When the app is running on environment B then the URLs for the REST API calls need to use hostname Y

I want to be able to define the variable for {{hostname}}

https://{{hostname}}/auth/realms/master/protocol/openid-connect/token

[neon-balcony]

By talking about environment A & B, they are physically separated docker instances?

[swright-eti]

Complete separated. Will be running in different Kubernetes clusters.

[neon-balcony]

Okay got it, currently you have to declare your REST API with difference hostname on each environment instance. And for each instance, this hostname can be declared only once.

But I assume that you would like to have something like a global instance config (maybe passed by docker environment settings)?

[swright-eti]

Configuring from Docker environment variables would be useful, but it should be scoped to each application. That way we could setup a Helm chart for each environment and pass in values to the pod/container at deploy time.

[neon-balcony]

Got it, I would summarize this feature as "global environment variables for self-hosted instances".

I've added that to our backlog, again, thanks for reporting this issue!

[swright-eti]

Perfect. Thanks so much for the quick response.