This message was deleted.
# general
s
This message was deleted.
d
this is for a
gcp.storage.Bucket
resource
b
you should be able to run a pulumi import and then look atthe details
it will give you a plan of what the import is and should give you the ability to test the details
d
any way to generate the code without having the resource loaded into state?
b
there's no dry run I'm afraid 😕
d
because right now, that would be massively useful (currently loading existing infrastructure into pulumi)
b
you can import it to an empty project, generate the code and remove the stack without running pulumi destroy
and it will do the same thing for you
d
yeah, thought that might be the workaround 😆
b
I wish I had better news 😄
d
I think Bucket imports might be broken when they have a cors policy set actually, always shows a diff (even if the code has
cors
unset). Will confirm in a minute
nope, works fine.
cors.method
is a list. To google, the order doesn't matter. But to pulumi, the order does matter. It'd be great to see resource diffs for imports though! I'm trying to keep manual operations to a minimum as I'm working across 3 stacks
b
I'm sure if you have suggestions, the team would love an issue in pulumi/pulumi repo with some good details on the use case 🙂
d
alas, it's a usecase we won't care about by the end of the year, as all the resources will already be managed by Pulumi. So I won't make a good stakeholder 🙂
b
You'd be surprised 🙂
d
Found out the diff does actually show for imports in the CLI output, just not in the pulumi dashboard