Hi, does anyone know what I need to do on the CLI ...
# general
s
Hi, does anyone know what I need to do on the CLI after transferring stacks from personal to organisation?
Copy code
$ pulumi stack history -s test   
error: no stack named 'test' found
How do I encode the organisation into the local files? Thx
m
Try using the "fully qualified stack name", notation is
<org>/<project>/<stack>
e.g.
catmeme/arti/sandbox.us-east-1
> How do I encode the organisation into the local files? Not sure exactly what you mean. Depends on your use case. In my use cases, I tend to pass the ORG in as an environment variable and use a Makefile to interpolate stack names.
s
Thanks, I was thinking something like:
Copy code
org: myorg
might go into Pulumi.yaml as an org default. is your $ORG env var just in your scripting?
m
The Makefile is the entrypoint to all common commands for software in the organization, to make moving between projects easier, with less cognitive load. Idea being a developer can bounce into any project regardless of the tech stack and expect some core commands, and for specific tech stacks some additional. So another project might deploy with Terraform or CloudFormation, or the application is TypeScript instead of Python, and the make entrypoints are the same:
Copy code
make build
make lint
make format
make test
make deploy
https://github.com/catmeme/arti/blob/main/Makefile#L30
s
Thanks, yes understood - I was just wondering if $ORG was something pulumi understood, but it's your wraparound tooling, thanks again.
full path worked, thank you
l
You can configure the default organization using this CLI command: https://www.pulumi.com/docs/cli/commands/pulumi_org_set-default/
s
Thanks @limited-rainbow-51650 - just what I was looking for.