Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Annotate credential with source backend #246

Closed
mih opened this issue Feb 18, 2023 · 0 comments · Fixed by #247
Closed

Annotate credential with source backend #246

mih opened this issue Feb 18, 2023 · 0 comments · Fixed by #247

Comments

@mih
Copy link
Member

mih commented Feb 18, 2023

With #224 planned, and the legacy backend already supported (even if not cleanly separated), it would be useful to know were credentials are coming from.

A concrete UX issue is that the credentials command reports legacy credential, even if they are not actually set. This is done, because it is the only way to communicate to users that they could even exist. But it is also confusing (they seemingly cannot be deleted).

Making them stand-out better would also make it possible to single them out and explain their nature better in the docs.
mih added a commit to mih/datalad-next that referenced this issue Feb 18, 2023
@mih
Annotate credentials with source backend label
8a5b9e2 
With this, we can now communicate to users what credentials are legacy
and behave different from others.

Closes datalad#246
@mih mih mentioned this issue Feb 18, 2023
Merged
@mih mih closed this as completed in #247 Feb 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve legacy credential handling (and test it) mih/datalad-next
1 participant
@mih