Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
o
orange-airport-64592
12/12/2022, 9:29 AMif I use the self-managed backend, does It not support the organization?
➜ test2 pulumi stack init broomllc/staging
warning: A new version of Pulumi is available. To upgrade from version '3.44.3' to '3.49.0', run
$ brew upgrade pulumi
or visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.
error: stack names may not contain slashese
echoing-dinner-19531
12/12/2022, 9:43 AMIt currently does not, it doesn't even support project parts of stack names currently. Self-managed is a flat structure.
o
orange-airport-64592
12/12/2022, 9:57 AM@echoing-dinner-19531 Thanks, do we plan to support ‘project/stack’ this style in the Self-managed backend?
e
echoing-dinner-19531
12/12/2022, 9:58 AMProbably eventually, although it might not be till 4.0
o
orange-airport-64592
12/12/2022, 10:01 AMyeah, that is good, If possible, I would like to contribute code. My pulumi code is a microservices architecture, so there are a lot of small projects that support different functions, but they all belong to dev or stage env
and they use the same backend which self-manged
e
echoing-dinner-19531
12/12/2022, 10:06 AMIf possible, I would like to contribute code.There are some pull requests open on the pulumi repo already to try and do this, it's mostly a case of the cost of ensuring it's backwards compatible and doesn't break existing users has been considered too high. I don't think that's anything that can really be helped with, and why this will probably be a 4.0 change with an explicit migration path.