EB Environment Variables from Github Secrets

[chronos-ohm]

Any way to pass environment variables to EB through just setting up the secrets on Github and defining them in the workflow yml, just like the AWS secrets are set?

Would be better if all the secrets were contained in one place.

[moon-sam]

I agree that they would be nice to have in one place, but one argument against that is there's no reason for github to ever know these secrets, since they aren't needed for deploy. They can be configured permanently in the AWS Beanstalk environment.

[nilansaha]

@moon-sam The secrets a pretty safe in Github for one and setting secrets in Github is a much easier job than setting them in AWS Beanstalk imo. I think this would be a great feature if added. Any plans for this @einaregilsson

[jleguina]

@einaregilsson Any updates on this? Cheers

[gbhand]

Sadly Einar is no longer with us #93 (comment) but @gzur has taken over maintaining the repo and is still actively reviewing PRs as they come in.

Environment variables could be set in this action in the UpdateEnvironment API call by adding environment variables to the OptionSettings request parameter.

Environment variables can also be set by including an .ebextensions config file with placeholder values filled in by GitHub Actions. Additionally for applications on the Docker platform you can override all environment variables by including a .env file in your application package.

[ameya-shahu]

Hi @gbhand , Could you please provide me some sample script?

[vitalykarasik]

I'm generating my '.env' from GitHub secret as simple as

echo '${{ secrets.ENV_FILE }}' > .env