worried-engineer-33884
11/04/2019, 7:13 PMcolossal-beach-47527
11/04/2019, 7:26 PMcurl
. For example:
export PULUMI_ACCESS_TOKEN="pul-..."
# Fully-qualified stack name, with organization
# project, and stack name.
export STACK="pulumi/get.pulumi.com/production"
curl -H "Authorization: token ${PULUMI_ACCESS_TOKEN}" \
<https://api.pulumi.com/api/stacks/$>{STACK}/export
worried-engineer-33884
11/04/2019, 7:26 PMcolossal-beach-47527
11/04/2019, 7:27 PM… /api/stacks/${STACK}/export/{version}
witty-yacht-82771
11/05/2019, 12:52 PMworried-engineer-33884
11/05/2019, 12:56 PMpulumi stack export > my-stack.json
witty-yacht-82771
11/05/2019, 1:09 PMcolossal-beach-47527
11/05/2019, 4:33 PM--stack
and --cwd
parameters to pulumi stack export
. So you can in theory export the checkpoint file of another stack you have access to, or perhaps in the context of running pulumi
from a different directory.witty-yacht-82771
11/05/2019, 4:34 PMcolossal-beach-47527
11/06/2019, 12:16 AMpulumi:pulumi:stack
or similar). We’ll probably add something like that when we start documenting the v1.0 of our REST API, but for now that’s the way to get a stack’s outputs.