This message was deleted.
# generals
sparse-intern-71089
09/08/2019, 2:09 AMThis message was deleted.
w
white-balloon-205
09/08/2019, 2:19 AM
I believe you can just use the
namet
tall-librarian-49374
09/08/2019, 2:29 AMIf you have any existing pulumi-defined resoures, you can run
pulumi stack export >> dump.txtidg
glamorous-printer-14057
09/08/2019, 2:56 AMyeah 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:t
tall-librarian-49374
09/08/2019, 2:59 AMInteresting... Create another temporary resource like this and check its id?
g
glamorous-printer-14057
09/08/2019, 3:02 AMoh good idea i’ll try that out
glamorous-printer-14057
09/08/2019, 5:50 AMfor 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
w
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 stacksNote that
ignoreChanges3 Views