High-Level Summary
We want to be able to support multiple Datum Cloud servers and authentications. Similar to how kubectl supports this with the use of clusters and contexts.
Currently, datumctl overwrite keys in the keychain, you can't have more than one auth session going at the same time. We want to fix this.
As part of that we will get to configuration file somewhere (example: ./datum/config.yaml) where users can annotate default flags for organization, namespace, project.
Motivation
Users may have Datum running in many different places (on-prem, our SaaS), internally for example there are multiple environments (stating, production). Or a single user may be part of many projects and organizations.
We want to serve a good and secure experience when it comes to move and remember the combinations of clusters, org and projects.
Goals
Have the datumctl being capable of moving between multiple Datum installations.
Non-Goals
No response
High-Level Summary
We want to be able to support multiple Datum Cloud servers and authentications. Similar to how kubectl supports this with the use of clusters and contexts.
Currently, datumctl overwrite keys in the keychain, you can't have more than one auth session going at the same time. We want to fix this.
As part of that we will get to configuration file somewhere (example:
./datum/config.yaml) where users can annotate default flags for organization, namespace, project.Motivation
Users may have Datum running in many different places (on-prem, our SaaS), internally for example there are multiple environments (stating, production). Or a single user may be part of many projects and organizations.
We want to serve a good and secure experience when it comes to move and remember the combinations of clusters, org and projects.
Goals
Have the datumctl being capable of moving between multiple Datum installations.
Non-Goals
No response