Use salt-call from salt bundle with transactional_update #602
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.
What does this PR do?
Backport of saltstack/salt#65204
What issues does this PR fix or reference?
In some cases if both salt bundle and classic salt package installed on the same system, transactional_update module can wrongly execute
salt-call
of classic salt packge instead of salt bundle which was used to process the event.What issues does this PR fix or reference?
Fixes: https://github.com/SUSE/spacewalk/issues/19875
Previous Behavior
Wrong
salt-call
executed inside the transaction while usingtransactional_update
.New Behavior
In case if the event processed with salt from the bundle
transactional_update
will callsalt-call
from the bundle explicitly.Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes/No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.