bright-orange-6940112/22/2019, 9:09 PM
on the S3 example template I attached:
error: preview failed
error: Preview failed: importing arnawss3::nuage test Error importing AWS S3 bucket policy: InvalidARNError: invalid ARN
caused by: invalid Amazon S3 ARN, unknown resource type, arnawss3:::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-6940112/22/2019, 9:56 PM
instead of the full ARN does not work either.
diagnostic returns an error:
warning: inputs to import do not match the existing resource; importing this resource will failAnd if I ignore it and
anyway, I get an error:
error: update failed
error: inputs to import do not match the existing resource
bright-orange-6940112/22/2019, 11:08 PM
The thing is though, that in Terraform you can import an S3 Bucket into your
without needing to define everything (diff will be calculated later).
You can actually use your
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
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 on