ambitious-father-68746
02/09/2021, 2:04 AMpulumi pre
is over in a minute, but the smallest change with pulumi up
, like updating just one resource, doesn't matter which, takes more than 30 minutes to run. This happens even if I use -t
. My backend is AWS. I've enabled some verbose logging and there is a lot of incoming output value translated
and incoming output property translated
, it seems to be covering the whole of the stack, once again even with -t
. It ends with a waiting for quiescence
with a counter on the upper hundreds going to zero, which I can't seem to be able to even find on Google. It almost feels like the whole of the stack is being processed even though there is a single change to be made. I'm not sure how to progress from here, having to wait between 30 minutes to an 1+ hour just to add an environment variable to a service is killing us. Any ideas? Thank you.No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by