dazzling-scientist-80826
09/21/2018, 9:32 PMbitter-oil-46081
09/21/2018, 9:33 PMpulumi stack export
2. Create a new stack with the same name in the target organization pulumi stack init <org-name>/<stack-name>
3. Import the stack you exported with pulumi stack import
4. Since secret configuration is encrypted with a key tied to the stack itself, you'll have to (unfortunately) run pulumi config set --secret <key> <value>
to reset any encrypted configuration you have.
5. You should now be able to pulumi stack rm
the old stack. You don't want to run pulumi destroy
.dazzling-scientist-80826
09/21/2018, 9:42 PMbitter-oil-46081
09/21/2018, 9:53 PMurn:pulumi:<old-stack-name>::
with urn:pulumi:<new-stack-name>::
.
@microscopic-florist-22719 Does that sound right to you?microscopic-florist-22719
import
will refuse to proceed if the stack name is incorrect, so at the very least we have belt and suspenders here.dazzling-scientist-80826
09/21/2018, 9:58 PMgit checkout
to get them backbitter-oil-46081
09/21/2018, 10:14 PMbut how do i backup my secret key for later?There's no concept of that today. The kye is created when a stack is initialized and managed by the service for the lifetime of the stack.
dazzling-scientist-80826
09/21/2018, 10:19 PMmicroscopic-florist-22719
dazzling-scientist-80826
09/21/2018, 10:20 PMmicroscopic-florist-22719
dazzling-scientist-80826
09/21/2018, 10:21 PM