This message was deleted.
# getting-started
s
This message was deleted.
m
Have any of the bucket properties changed?
(For example, the resource name? That's the first argument,
demo-bucket
in your code.)
If so, that would cause the bucket to be deleted and replaced.
b
Here's the output, I think I may have fixed the bucket from deletion but the files are still attempting to be deleted + ├─ awsxecsFargateService service create + │ ├─ awsxecsFargateTaskDefinition service create + │ │ ├─ awscloudwatchLogGroup service create + │ │ ├─ awsiamRole service-execution create + │ │ ├─ awsiamRole service-task create + │ │ ├─ awsiamRolePolicyAttachment service-execution-9a42f520 create + │ │ └─ awsecsTaskDefinition service create + │ └─ awsecsService service create - ├─ awss3BucketObject file-1 delete - ├─ awss3BucketObject file-2 delete - └─ awss3BucketObject file-3 delete
m
I don't see any cod for the bucket objects themselves in your example. What created them? Was there code there previously that created them that's no longer in the program? If so, that would cause Pulumi to want to remove them as well. (Removing resource declarations from the code, like renaming them, is is like telling Pulumi "I don't want these anymore".)
🫡 1
You can "retain" them, however, if you want to be able to remove them from the code but not delete them: https://www.pulumi.com/docs/concepts/options/retainondelete/
... but to do that, you need to update them first to add the
retain_on_delete
option
b
yes the original lines were removed that added the files from the local directory, given it seemed a bit excessive after they were already uploaded. Can this be used on the s3?
retain_on_delete
m
It's available on all Pulumi resources, yep
👍 1