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

provider/aws: Fix issue when changing map-public-ip in Subnets #1234

Merged
merged 3 commits into from
Apr 6, 2015

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Mar 18, 2015

This should fix #671 (partially?) by actually reading the map_public_ip_on_launch config var when making a change.

@catsby
Copy link
Contributor Author

catsby commented Mar 18, 2015

AWS Defaults this value to false. I wonder if adding Default to this would be appropriate.

@phinze
Copy link
Contributor

phinze commented Apr 1, 2015

AWS Defaults this value to false. I wonder if adding Default to this would be appropriate.

Since booleans are so tricky w/ Computed, I think it might be saner to add a Default: false and remove Computed.

…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
  ...
@catsby
Copy link
Contributor Author

catsby commented Apr 1, 2015

I think it might be saner to add a Default: false and remove Computed.

@phinze done

@phinze
Copy link
Contributor

phinze commented Apr 6, 2015

LGTM

catsby added a commit that referenced this pull request Apr 6, 2015
…hange

provider/aws: Fix issue when changing map-public-ip in Subnets
@catsby catsby merged commit fa2d41e into master Apr 6, 2015
@catsby catsby deleted the b-fix-aws-subnet-map-public-change branch April 6, 2015 16:03
@danielward danielward mentioned this pull request May 12, 2016
Closed
@azdevops azdevops mentioned this pull request Jun 5, 2017
@derekmaurer derekmaurer mentioned this pull request Jun 8, 2017
@johntdyer johntdyer mentioned this pull request Jul 17, 2017
@ghost
Copy link

ghost commented May 3, 2020

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 ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws subnet VPC forced to change when using "map_public_ip_on_launch" field
2 participants