Open
Conversation
This commit contains the foundation of being able to connect to multiple Datum clusters and to switch in between projects and orgs via contexts.
gianarb
force-pushed
the
feat/persistent-layer
branch
from
5d0143a to
b7a94b1
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This commit contains the foundation of being able to connect to multiple
Datum clusters and to switch in between projects and orgs via contexts.
This PR at the time you run this new version of the datumctl will create the
configuration file without breaking compatibility with your current authorized
login.
Every time you run login it will check if it knows the server you are connecting
to, if not it will add it to the list and create a context for you to use.
commands
A couple of new commands related to context and clusters are available under
configsubcommand.Now that authenticated user are related to context I don't think we need the
auth listand even less theauth switchin order to avoid confusions so I removed themLimitation:
Currently, we do not have a way to discriminate when to reach the organization
control plane or the project one. It means that we can not accept project AND
org into the same context, only one can be set. Right now we prioritize project
because most like it is the one you want to use for the most.
User who wants to quickly switch in between org and project needs to create
multiple context.
Fixes datum-cloud/enhancements#653