You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My question is very simple, since (taking GitHub as code source) a repo can be built directly from the source code into a docker image, there is really no way to inject any environment variables into it, the only way (I know of) is through the environment tab in the deployment management panel. However would it be considered best practice to put the env variables and secrets there too? In this context a env variable is an environment variable with non-sensitive data while the env secret holds sensitive values (using GitHub terminology).
Thanks in advance for sharing your opinion and tips!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi team!
My question is very simple, since (taking GitHub as code source) a repo can be built directly from the source code into a docker image, there is really no way to inject any environment variables into it, the only way (I know of) is through the environment tab in the deployment management panel. However would it be considered best practice to put the env variables and secrets there too? In this context a env variable is an environment variable with non-sensitive data while the env secret holds sensitive values (using GitHub terminology).
Thanks in advance for sharing your opinion and tips!
Beta Was this translation helpful? Give feedback.
All reactions