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.

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

Propagate remote options through schema 1 copies #1007

Merged
merged 1 commit into from
Apr 28, 2021

Conversation

jonjohnsonjr
Copy link
Collaborator

@jonjohnsonjr jonjohnsonjr commented Apr 28, 2021

The schema 1 copying code was very hacked together, but remote.Put
simplifies things a bit. This extends some of the crane/gcrane options
down through to legacy.CopySchema1.

Fixes #1006

The schema 1 copying code was very hacked together, but remote.Put
simplifies things a bit. This extends some of the crane/gcrane options
down through to legacy.CopySchema1.
@jonjohnsonjr
Copy link
Collaborator Author

Thanks @deitch your change to add #980 helped a lot and got rid of a TODO 😄

@jonjohnsonjr jonjohnsonjr merged commit a58f1d5 into google:main Apr 28, 2021
@jonjohnsonjr jonjohnsonjr deleted the gcrane-schema1 branch April 28, 2021 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

schema 1 copies always use default keychain
2 participants