-
Notifications
You must be signed in to change notification settings - Fork 156
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
Not able to import aws.directconnect.GatewayAssociation #3670
Comments
Hi @dennispan, sorry you are having this issue. It looks like the generated code for the import is not quite right - the resource accepts only one of LMK if you are still having issues after doing that! |
Thanks @VenelinMartinov ! That's a great tip. Indeed we are making some progress, but still getting error. We manually imported the
Here's the error when I run
I double checked the account id etc. and they are correct. Is there debug log that can be used to see what Pulumi thinks doesn't match the existing resource? |
Hi @dennispan, from the output there:
It looks like the resource should not have
How are you importing the resource? Doesn't pulumi print code for you with the right properties when you do EDIT: My bad, I see now you are using the Instructions for the GatewayAssociation resource are here: https://www.pulumi.com/registry/packages/aws/api-docs/directconnect/gatewayassociation/#import |
Toward #1225 - this fixes the special case of ConflictsWith warnings. This fixes spurious warnings on `pulumi import`, popular bugs such as: - pulumi/pulumi-aws#2318 - pulumi/pulumi-aws#3670 - pulumi/pulumi-gitlab#293 - pulumi/pulumi-gcp#844 - pulumi/pulumi-linode#373 TF does not guarantee Read results to be compatible with calling Check on, in particular Read can return results that run afoul of ConflictsWith constraint. This change compensates by arbitrarily dropping data from the Read result until it passes ConflictsWith checks. This affects `pulumi refresh` as well as I think it should although I have not seen "in the wild" cases where refresh is affected, since it typically will not copy these properties to the input bag unless they're present in old inputs, which are usually correct wrt to ConflictsWith.
Hey @dennispan, we recently released changes that should improve warnings on imports as part of release v6.36.0. Could you please have another try with that version? Thanks! |
|
I just tried to run the same import but unfortunately I am not able to get back to the previous state and let the same warning message to show up. We can close this and I will for sure report back if something similar happens |
What happened?
We are looking to import an existing gateway association (
GatewayAssociation
), and the related gateway association proposal (GatewayAssociationProposal
). But importingGatewayAssociation
keeps failing with this error:Example
This is the code:
I double checked the proposal id
474b56b8-3b67-479a-a8ea-5d1f438cd1c7
is correct. Also checked the direct connect and virtual gateway id.Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: