This message was deleted.
# aws
s
This message was deleted.
g
I noticed that importing with protection was too problematic for me. Import didn't fetch all the data and
pulumi up
would want to update some attributes during next run. I'd suggest to unprotect imported resources and check changes with
pulumi preview --diff
first, before running
pulumi up
Later, when your infrastructure is stable and there are no changes in preview I'd consider protecting crucial resources.
https://www.pulumi.com/docs/cli/commands/pulumi_import/ when importing you can set
--protect=false
flag