-
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
AWS AppStream FleetStackAssociation destroy not working #1966
Comments
You don't happen to have a full pulumi program we could run to repro this? The snippet above is dependent on a load of variables that you've removed so can't actually be run. |
this is possibly related to hashicorp/terraform-provider-aws#22625 (?). But I'm not sure. other than the subnet and the image name (which I can't imagine would make a difference), is there anything else missing? You could use this as the image name if you want a specific example Here's the VPC/subnet. Although I've tried it with others and same issue.
|
@eli88fine I'm trying to run this program - how do I provide this image arn? I'm not super familiar with appstream... Thank you!
|
You can use |
Okay I was able to mostly repro this with the following program:
I believe it's a provider issue so I'll move it to |
Here's the workaround I found in the meantime, if other people run across this same problem (using the Pulumi Command plugin):
|
Just FYI, upstream issue (hashicorp/terraform-provider-aws#22625) has been resolved. |
Great! Is there a specific minimum version of pulumi AWS that will use that patched version of terraform? |
This has been released as part of pulumi-aws v5.10.0 - thanks for the reminder here @zulizzi-cfg |
What happened?
I'm spinning up a Stack, Fleet, and StackFleetAssociation. That works fine to spin it up, but when I try and destroy it, it won't tear down because the Stack & Fleet can't be deleted while still associated, but the Association isn't being deleted. I even explicitly added
depends_on
, although that seems like in theory it should be superfluous because the stack and fleet names are already required arguments to the Association.Steps to reproduce
Expected Behavior
calling destroy destroys the stack
Actual Behavior
The text was updated successfully, but these errors were encountered: