Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
l
little-cartoon-10569
09/21/2020, 5:17 AMNoticed 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.
g
gentle-diamond-70147
09/21/2020, 3:27 PMSounds like a bug in our representation of the
Directoryl
little-cartoon-10569
09/21/2020, 10:22 PMIs there enough info here? https://github.com/pulumi/pulumi-aws/issues/1127