Very helpful. Is it possible to automate the parameter store based on environment configuration ie when configuration changes in git, parameter store is updated and service updated.
sorry for delayed response, yes it is possible if you use code pipeline which monitors changes in git and use code deploy to reference those parameters
Values are generating into container, but how to define these keys into code? Im working on java maven environment, how to configure key names in the code?
Env Values are set in task definition and are available within the newly running container’s environment (printenv). Trying to access the env var in NextJS console.log(process.env.NEXT_PUBLIC_TOKEN_VALUE). It’s undefined
awesome explanation, thank you. i really see all i need in env vars now
Really great video..helped me in the most needed moment.
Glad you survived 😉 don’t forget to subscribe!
Very helpful. Is it possible to automate the parameter store based on environment configuration ie when configuration changes in git, parameter store is updated and service updated.
sorry for delayed response, yes it is possible if you use code pipeline which monitors changes in git and use code deploy to reference those parameters
Values are generating into container, but how to define these keys into code?
Im working on java maven environment, how to configure key names in the code?
I'm sure you must know how to pass vars to your docker container ?
No please explain
What terminal or terminal extension are you using, looks very helpful
I'm using Iterm with fig.io/ extension
can we use same for eks and in terraform ??
yes we should be able to do it
Which terminal are you using?
wrap
Very nice
Env Values are set in task definition and are available within the newly running container’s environment (printenv). Trying to access the env var in NextJS console.log(process.env.NEXT_PUBLIC_TOKEN_VALUE). It’s undefined
may be check your nextjs config next.config.js file which should include the above env variable