-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Expose additional migration APIs #8153
Conversation
93f092e
to
d63061d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I take this is mostly moving things around and apart from the comment below I do no see anything problematic. Also note that this is not code I'm familiar with, but it does not seem to change much anyways.
@hsanjuan This PR is really just moving things around, to make them accessible for doing things like #7658. I have added a comment in the code to offer an explanation for the confusing construct you pointed out, but if you have any suggestions about a better way to do this (given the explanation) I would love to improve that code. |
Expose migration APIs for reading migration config and creating migration fetchers. This allows implementation of commands and external applications that want to retrieve migrations according to the Migration portion of the IPFS config. This change also moves some functionality that is specific to fetching migrations via IPFS into the `ipfsfetcher` package.
5e05ba6
to
1ca7b76
Compare
bump |
Expose migration APIs for reading migration config and creating migration fetchers. This allows the implementation of commands and external applications that want to retrieve migrations according to the Migration portion of the IPFS config.
This change also moves some functionality that is specific to fetching migrations via IPFS into the
ipfsfetcher
package.This PR is also a prerequisite for expanding the functionality of #7658