-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_dx_gateway_association_proposal recreated #9209
Comments
A solution here may be to modify the behavior of the |
@saliceti How urgent is this to address? Thanks. |
We stopped using this resource and replaced it with boto code triggered by a provisionner. |
To be honest this resource is not useful in the current state. If no plan is made to fix it soon it should be removed in the meantime. |
I've just run into this problem as well. I tend to agree with @saliceti - this resource should be fixed or removed, as this bug is not obvious and has the potential to cause outages. |
Just ran into this issue too. Terraform created a new proposal and detached the VPC from the Direct Connect Gateway. |
I have also ran into this issue. It should be fixed as soon as possible. Anywork around for now? |
We're also seeing this issue, we would prefer to avoid any messy work arounds obviously :) |
…rks even if expired" This reverts commit c13b25c.
Looking at this some more the possibility I see is to change |
Same issue for me using the latest terraform version |
I'm experiencing the same issue with terraform version |
Encountered this too, going to omit until fixed. |
Does anyone know if this has been fixed? It's still causing us a lot of grief. |
Nope the PR is still open, I've been waiting months for this to get fixed |
I worked around the proposal recreation like this for now. It's not nice but it's at least usable.
After the initial association is created one needs to update the variable proposal_id to the output value. The proposal will not be recreated in the future and the association is not recreated either. I did not test this yet with a new association, ony with associations that the proposal_id has been deleted by AWS. |
…rks even if expired" This reverts commit c13b25c.
This has been released in version 3.29.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 for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Terraform bug
It happens when associating a virtual private gateway with a direct connect gateway in a separate account (See AWS doc). There is a terraform resource for the proposal. But this resource is not permanent, so terraform will try to recreate it.
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
terraform plan
: shows creation of the proposal and recreation of the associationImportant Factoids
Raised a support case with AWS to understand the behaviour. Here is the response:
I relayed the same question to the service team and they have informed me that the proposal will be available as long as the "accepter" has not accepted the proposal. Once the proposal is accepted, it will disappear after some time. There is no defined time duration as to how long the proposal is available after acceptance through CLI. As we use a distributed and eventual consistency model, I would highly recommend you to not use the time the proposal remains in the CLI output after acceptance to make any design, architectural, or application decisions.
The text was updated successfully, but these errors were encountered: