-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add gitfs and git_pillar fallback branch #51971
Conversation
Exactly what I need! +1 for this PR. Thanks @sathieu |
@hakanf If you're using GitPython, you can already test it. PyGit2 is not done yet |
@sathieu , yes I am using gitpython, and I have already begun to use the patch. It does indeed seem to work as expected... |
2ebe0c7
to
30bd3be
Compare
@terminalmage @dwoz, please review. I've added tests too. |
89ba19b
to
097f6c7
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.
Thanks for the PR! I found a couple of small typos in the docs portion.
d233ff4
to
f6fb380
Compare
@waynew Comments addressed. |
@waynew @dwoz @frogunder Any chance to have this in neon? |
thanks, i'll dive in. I'll try today, but most likely wont get to it till Monday. When i was troubleshooting I was using ubuntu18, so I'm guessing a different state is failing on centos7 during setup of the gitfs server. |
I'm pretty sure i see the issue and working on a fix. might not have it ready till tomorrow. |
Set venv_bin for gitfs test setup if virtualenv exists
@Ch3LL thanks ! |
@Ch3LL looks like we've got one failure - https://jenkinsci.saltstack.com/job/pr-kitchen-centos7-py3/job/PR-51971/14/testReport/junit/integration.states.test_virtualenv_mod/VirtualenvTest/test_issue_1959_virtualenv_runas/ @sathieu Looks like we're out of date with neon here, would you like to rebase, or just merge neon into your branch? |
Merge Neon into fallback
✨ ✨ |
@waynew Thanks! |
Despite this merge request was merged into neon, it is neitehr part of the 3000 release or the master branch:
@sathieu Can you please rebase your pull request against the master branch? |
@bdrung It's listed on https://github.com/saltstack/salt/projects/5 @dwoz How to move forward on this? |
@sathieu It's listed under "PR needs port to master". So I think that rebasing your patch set on top of master and creating another pull request would be a way to move forward. |
Add a fallback branch when no matching branch is found. Example: ```yaml gitfs_remotes: - http://foo.com/states/top.git: - all_saltenvs: master - http://foo.com/states/apache.git: - fallback: master - http://foo.com/states/nginx.git: - fallback: master - http://foo.com/states/webapp.git: - fallback: develop ``` Where a state in `webapp` includes a state of `apache`. With this change, one can test a feature branch of `webapp` without needing to create the same branch in `apache`. Similarly, one can test a feature branch of `apache` without needing to create the same branch in `webapp`. This is a forward port of pull request saltstack#51971 from Mathieu Parent. Signed-off-by: Benjamin Drung <benjamin.drung@cloud.ionos.com>
I forward-ported this merge request in #56647, which took a lot of time due to a lot of merge conflicts due to blackening the code. |
What does this PR do?
Add a fallback branch when no matching branch is found
What issues does this PR fix or reference?
New Behavior
Example:
Where a state in
webapp
includes a state ofapache
.With this PR, one can test a feature branch of
webapp
without needing to create the same branch inapache
. Similarly, one can test a feature branch ofapache
without needing to create the same branch inwebapp
.Tests written?
Yes
Commits signed with GPG?
Yes