-
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
provider/aws: Fix issue when changing map-public-ip in Subnets #1234
Conversation
AWS Defaults this value to |
Since booleans are so tricky w/ Computed, I think it might be saner to add a |
…map-public-change * upstream/master: (295 commits) Update CHANGELOG.md provider/aws: Allow DB Parameter group to change in RDS return error if failed to set tags on Route 53 zone core: [tests] fix order dependent test Fix hashcode for ASG test provider/aws: Fix issue with tainted ASG groups failing to re-create Don't error when reading s3 bucket with no tags Avoid panics when DBName is not set Add floating IP association in aceptance tests Use env var OS_POOL_NAME as default for pool attribute providers/heroku: Add heroku-postgres to example docs: resource addressing providers/heroku: Document environment variables providers/heroku: Add region to example Bugfix on floating IP assignment Update CHANGELOG.md update CHANGELOG website: note on docker core: formalize resource addressing core: fill out context tests for targeted ops ...
@phinze done |
LGTM |
…hange provider/aws: Fix issue when changing map-public-ip in Subnets
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. |
This should fix #671 (partially?) by actually reading the
map_public_ip_on_launch
config var when making a change.