This message was deleted.

sparse-intern-71089

09/08/2019, 2:09 AM

This message was deleted.

white-balloon-205

09/08/2019, 2:19 AM

I believe you can just use the

name

of the cloud formation stack.

tall-librarian-49374

09/08/2019, 2:29 AM

If you have any existing pulumi-defined resoures, you can run

pulumi stack export >> dump.txt

and study the

id

properties in there. AWS IDs are simple names as far as I can tell.

glamorous-printer-14057

09/08/2019, 2:56 AM

yeah this particular resource (our Buildkite CloudFormation stack) was created manually, and I’m trying to get it under Pulumi management—however both the name of the existing stack and the

arn:

don’t seem to work

tall-librarian-49374

09/08/2019, 2:59 AM

Interesting... Create another temporary resource like this and check its id?

glamorous-printer-14057

09/08/2019, 3:02 AM

oh good idea i’ll try that out

glamorous-printer-14057

09/08/2019, 5:50 AM

for future reference, the issue here was that I wasn’t explicitly specifying a provider, and my existing CF stacks were in another AWS region 🤦‍♂️ that said, it’s kind of tricky to get the CF template YAML to perfectly match the existing, manually-created CF stacks, so I’m just going the route of recreating them in Pulumi and deprecating our previous CF stacks

white-balloon-205

09/08/2019, 2:31 PM

t’s kind of tricky to get the CF template YAML to perfectly match the existing, manually-created CF stacks

Note that

ignoreChanges

might help here = depending on what your goal was in trying to import these into Pulumi in the first place.

3 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.