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.

Pulumi Community

hey, we seem to have gotten pulumi into a flaky state after importing manually created aws resources. It rarely deploys, replaces unchanged things, fails updates etc. Repeatedly re-running pulumi sometimes works. Any pointers? :slightly_smiling_face: It's a ts awsx classic project that's been running flawlessly basically unchanged for years. Diff in thread

only diff I can see in `pulumi stack export --file` (other than reordering items) is:

`urn:pulumi:prod::lesslie-backend::awsx:ecs:FargateService$aws:ecs/service:Service::backend` -&gt; `outputs` -&gt; `networkConfiguration` -&gt; `subnets` is sometimes an empty array and sometimes contains two subnets. The corresponding input subnet id array is empty.

Are you running refreshes? If you are, are there differences between code and AWS?