Temporarily revert support for projects in the Self-Managed backend #12052
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
justinvp
added
the
impact/no-changelog-required
abhinav
approved these changes
Feb 2, 2023
Changelog[uncommitted] (2023-02-03) |
|
bors merge p=1 |
|
Superseded by #12066 |
|
bors r+ |
|
Already running a review |
|
Accidentally closed the wrong PR |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Temporarily reverting this to keep master in a releasable state while we finalize the design.
As it was, the syntax
pulumi stack select foo/barcould mean fundamentally different things based on what backend you're logged into. In the Service backend, thefoois the org. In the Self-Managed backend, thefoowould be the project name. Moreover, in the Service backend, there is one "fully-qualified" name, and all the others are just shorthands. But this wouldn't be true in the Self-Managed backend wherebarrepresents a fundamentally different stack thanfoo/bar. This makes it hard to explain what stack identities are. Self-Managed has been a pure subset of what Service supported in terms of stack identities. If we went with this design, it would be a partially overlapping, but inconsistent subset/superset.We're discussing some design alternatives that would make stack identities in the Self-Managed backend more consistent with the Service backend, and will reintroduce the changes with the adjusted design soon.