Feature: Manipulating variables during runtime#10
Open
MrMarvin wants to merge 1 commit intoconversis:masterfrom
Open
Feature: Manipulating variables during runtime#10MrMarvin wants to merge 1 commit intoconversis:masterfrom
MrMarvin wants to merge 1 commit intoconversis:masterfrom
Conversation
WIP implementing variableExtractor adds section about variable manipulation
|
I currently have the same thing set up with custom grains, but it requires 2 runs (one to apply the custom grain extractor, one to retrieve the new grains) so this would be ideal. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With this PR, varstack will be able to use custom python modules that are run on every stacking to manipulate the available variables.
Our use case for this feature is that we run varstack with saltstacks salt and do not want to extract any parts of our minions id (in the 'id' grain) on the client side. With our custom module in varstack we are now able to only send the minion id and let varstack extract it into different parts like location, cluster_id and whatever is coded into the minions fqdn/id. The provided example is based on our use case.
Tests are included and green + there is an example and README section. As this is an opt-in feature, it should not break any current varstack installations.