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

schema 1 copies always use default keychain #1006

Closed
jonjohnsonjr opened this issue Apr 28, 2021 · 0 comments · Fixed by #1007
Closed

schema 1 copies always use default keychain #1006

jonjohnsonjr opened this issue Apr 28, 2021 · 0 comments · Fixed by #1007

Comments

@jonjohnsonjr
Copy link
Collaborator

This is not ideal for gcrane cp, as schema 1 copies use different credentials than every other media type, which is very confusing.
@jonjohnsonjr jonjohnsonjr changed the title schema 1 copies always uses default keychain schema 1 copies always use default keychain Apr 28, 2021
@jonjohnsonjr jonjohnsonjr mentioned this issue Apr 28, 2021
Merged
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.

Propagate remote options through schema 1 copies jonjohnsonjr/go-containerregistry
1 participant
@jonjohnsonjr