Support fetching yml config file from remote repository #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://dimagi-dev.atlassian.net/browse/CDTW-29
Since moving staging config files to the staging-branches repository, this has been on the list of things to do.
The jist of this PR is converting this logic in the rebuildstaging script:
to python in git-build-branch, and allowing the caller to pass in the necessary info for this. Having this logic in git-build-branch instead of the rebuildstaging bash script that calls git-build-branch lays the groundwork for automating branch removal in git-build-branch as well.
I left the
config_path
untouched for now to avoid any breaking change togit-build-branch
, but I do think it makes sense to make that an optional keyword argument that can be used instead of the remote repo arguments. It could even make sense to do so in this PR, but wanted to get thoughts from others.