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

[Bug]: aws_ec2_host attempts to replace resource when an outpost_arn is specified without an asset_id #33140

Closed
silvaalbert opened this issue Aug 22, 2023 · 3 comments · Fixed by #33142
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@silvaalbert
Copy link
Contributor

Terraform Core Version

1.5.5

AWS Provider Version

5.13.1

Affected Resource(s)

  • aws_ec2_host

Expected Behavior

No changes should be expected/reported

Actual Behavior

Resource is attempted to be replaced

Relevant Error/Panic Output Snippet

-/+ resource "aws_ec2_host" "test" {
      ~ arn               = "arn:aws:ec2:us-west-2:123456789012:dedicated-host/h-0c92b3d68d7154631" -> (known after apply)
      - asset_id          = "1234567489" -> null # forces replacement
      ~ id                = "h-0c92b3d68d7154631" -> (known after apply)
      ~ owner_id          = "123456789012" -> (known after apply)
      - tags              = {} -> null
      ~ tags_all          = {} -> (known after apply)
        # (5 unchanged attributes hidden)
    }

Terraform Configuration Files

n/a

Steps to Reproduce

  1. Deploy a dedicated host specifying only the outpost_arn
  2. Run a terraform plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

Yes

@silvaalbert silvaalbert added the bug Addresses a defect in current functionality. label Aug 22, 2023
@github-actions github-actions bot added the service/ec2 Issues and PRs that pertain to the ec2 service. label Aug 22, 2023
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 22, 2023
@ewbankkit ewbankkit removed the needs-triage Waiting for first response or review from a maintainer. label Aug 22, 2023
@github-actions github-actions bot added this to the v5.14.0 milestone Aug 23, 2023
@github-actions
Copy link

This functionality has been released in v5.14.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants