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
[Bug]: Don't associate public ip when eip is assigned to instance #37318
Labels
bug
Addresses a defect in current functionality.
service/ec2
Issues and PRs that pertain to the ec2 service.
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
github-actions
bot
added
the
service/ec2
Issues and PRs that pertain to the ec2 service.
label
May 7, 2024
terraform-aws-provider
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
May 7, 2024
Related #37238 |
justinretzolk
removed
the
needs-triage
Waiting for first response or review from a maintainer.
label
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Addresses a defect in current functionality.
service/ec2
Issues and PRs that pertain to the ec2 service.
Terraform Core Version
1.7.5
AWS Provider Version
4.25
Affected Resource(s)
aws_eip, aws_instance
Expected Behavior
After applying the next plan (an aws_instance with eip) in this manner:
All goes like estimate, istance has correctly the eip1 public eip, but if a plan is executed after this, the associate_public_ip_address directive force the replacemente of the instance, and the only way to correct this is to comment out or put associate_public_ip_address to true.
Is this behavior correct or a bug? I can't figure how this can be correct, but not having strong experience, preferring to ask to the community
Actual Behavior
The instance is correctly created, but every next plan, requires the istance to be replaced.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: