-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Removing Elastic Beanstalk Environment Variables #6890
Labels
Comments
apparentlymart
changed the title
Removing Beanstalk Environment Variables
Removing Elastic Beanstalk Environment Variables
May 26, 2016
catsby
added a commit
that referenced
this issue
Jul 22, 2016
Fixes the logic that updated settings for Elastic Beanstalk Environments. Because the update is done in the same API call, we need to split removals / additions. Fixes #6890
+1 I just ran into this problem, can we see to it that it's fixed.
Thanks. |
catsby
added a commit
that referenced
this issue
Jul 28, 2016
Fixes the logic that updated settings for Elastic Beanstalk Environments. Because the update is done in the same API call, we need to split removals / additions. Fixes #6890
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Apr 23, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On terraform 0.6.16
If I remove a
setting
with the namespace ofaws:elasticbeanstalk:application:environment
, terraform says its removed, however the AWS console still has that setting, as well as the API still returns a value for that setting.Also, if I add a environment variable manually in the AWS console and then re-run a plan, terraform doesn't seem to see that value and try to remove it.
It looks like when terraform refreshes its state from AWS, it doesn't properly catalog
aws:elasticbeanstalk:application:environment
keys, certainly not ensuring that there are not extra or missing keys.The text was updated successfully, but these errors were encountered: