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

Noticed while investigating the Directory stuff: in the SDK and console, Directory is not taggable. But in Pulumi, it is. Any changes to tags cause Pulumi to try to replace your Directory. Deleting AD because a doesn't-really-exist property has changed probably isn't ideal?

I have use a StackTransformation to tag everything that's taggable, and that was half the reason Pulumi wanted to delete AD. I've edited my state to remove tags, but now Pulumi wants to re-apply them because of my StackTransformation. I'll go edit that now to explicitly ignore Directory.

Removing it from the list of taggable resources worked.

Sounds like a bug in our representation of the `Directory` service. Mind opening an issue at <https://github.com/pulumi/pulumi-aws> ?

Is there enough info here? <https://github.com/pulumi/pulumi-aws/issues/1127>