Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Migrated] Allow environment variable expansion in settings #813

Closed
jneves opened this issue Feb 20, 2021 · 1 comment
Closed

[Migrated] Allow environment variable expansion in settings #813

jneves opened this issue Feb 20, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@jneves
Copy link
Contributor

jneves commented Feb 20, 2021

Originally from: Miserlou/Zappa#1982 by gdavoian

I'd like to use aws_environment_variables to set some native Lambda environment variables automatically without logging into the AWS console, but I don't want to hard-code any sensitive values to the zappa_settings.json. Ideally, I'd like to use something like "key": "${value}", and then have Zappa substitute value from the current environment on deploy/update. I'm not sure whether this is already supported or whether it really makes sense to add support for this.

@monkut monkut added the duplicate This issue or pull request already exists label Aug 18, 2022
@monkut
Copy link
Collaborator

monkut commented Aug 18, 2022

marking as duplicate of:
#988

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants