sparse-intern-71089
12/22/2019, 9:09 PMwhite-balloon-205
nuage-test
as the import id. Iām surprised the error is so bad - but I expect it will work with the name instead of the ARN.bright-orange-69401
12/22/2019, 9:56 PMnuage-test
instead of the full ARN does not work either.
The pulumi preview
diagnostic returns an error:
Diagnostics:
awss3Bucket (nuage-test):
warning: inputs to import do not match the existing resource; importing this resource will failAnd if I ignore it and
pulumi up
anyway, I get an error:
Diagnostics:
pulumipulumiStack (nuage-admin-dev):
error: update failed
awss3Bucket (nuage-test):
error: inputs to import do not match the existing resource
white-balloon-205
bright-orange-69401
12/22/2019, 11:08 PMcors_rules
The thing is though, that in Terraform you can import an S3 Bucket into your .tfstate
without needing to define everything (diff will be calculated later).
You can actually use your .tfstate
to fill the missing values in your template and avoid the diff, which saves a huge amount of time.
It's a pretty big issue (IMHO) that you can't do the same thing in Pulumi.
I actually had to copy into Pulumi the cors_rules
from the state I imported into Terraform, as it is quite difficult to list the exact rules with just the AWS Console & Pulumi's docs
In terms of UX, it would be great to be able to manually set up some Cloud resources, easily pull the configs using the CLI and then use that as boilerplate to get everything under Pulumi management and extend it programatically from there onwhite-balloon-205