Hi, in the last couple of weeks I've noticed that ...
# general
a
Hi, in the last couple of weeks I've noticed that sometimes, when using
--target
, both
pulumi pre
and
pulumi up
will show only the resources that I want to update (good), but after confirming that I want to perform the update, Pulumi will try to update a resource that I haven't explicitly requested, causing failures. Has anyone seen this behaviour before?
b
i haven't seen this, but if you can do an asciinema or video recording of this and file an issue it would be invaluable
a
OK, will do. I was also "lucky" enough to get this last breakage on a mostly unused stack, so I'm trying to break the code down to a reproducible state.
Turns out it's very reproducible, but it's a problem with the AWS provider, not Pulumi