Enable sharing of history #226
Unanswered
richardcase
asked this question in
Ideas
Replies: 1 comment 1 reply
-
Think this is a great idea. We also need to think about merging a users existing history with the imported one, and check for alias duplication/clashes etc |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Should we enable the sharing of history so that team members can share common cluster connection information?
For example, it could work something like this:
kconnect use
and sets aliaseskconnect history export --aliases cluster1,cluster2 -f export.yaml
)kconnect history import -f export.yaml --user newusername --overwrite
)When importing we'd need to overwrite the username or on export have an option to blank the username.
What do you think @rajarajanpsj @seankelly001?
Beta Was this translation helpful? Give feedback.
All reactions