Adding a merge_all function to slsutil #47679
Merged
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.
The merge_all function merges a list of objects in order. This will make merging multiple objects more readable. Consider the difference between merging three objects with
slsutil.merge
versus merging withslsutil.merge_all
With
slsutil.merge
:With
slsutil.merge_all
:I'm interested to know if you all think it would be better to add this function or to overload the merge function.
What does this PR do?
This PR adds a merge_all function to the slsutil module
What issues does this PR fix or reference?
None
Tests written?
No
Commits signed with GPG?
Yes
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.