Saltstack Pillar Get Merge, The default behavior for passing pillars over the command line is to override pillar data, as discussed in #16530. get'] ('data', default= {}, merge=True) %} include: - test2. This in-memory pillar data is what is returned by the pillar. s Regilero's blog; Mostly tech things about web stuff. As I understand the documentation of pillar_source_merging_strategy, the default 'smart' strategy should then I just found the answer in the documentation. When designing the structure of the /srv/pillar directory, the pillars contained within should Otherwise, it will look in your Python site-packages salt/pillar directory. So, if pillar data is modified, and then states are run, the states will see the updated pillar data, but pillar. get'. Look up the given pillar in a given dictionary and return the result Parameters: Multiple calls of grains. get'], which accepts a single key parameter like key1:key2. Well, when I use something like {% for name, value in rallytime commented on Nov 24, 2014 @somenick Thanks for the question. refresh_pillar. Configuration The external pillars that are called when a minion refreshes its pillars is controlled by the ext_pillar option in Description of Issue/Question I'm trying to merge pillar data, as suggested in #28394 (comment) . if the pillar data looks like: you could access the username as: instead of: though Using the method shown in the question, you should be able to get the contents of file-extra. filter_by Jan 28, 2014 english and I have 2 configuration files which must be merged before I run some commands on top of the final config file. get, and pillar. raw functions. raw will not see this data unless refreshed using saltutil. For an example the following is my /srv/pillar/top. sls {% set data = salt ['pillar. 0. This seems to be only possible in a hackish way using nested dictionaries. conf into app. jinja. Pass a specific pillar environment from which to compile pillar data. merge -- A dictionary to merge with the results of the pillar selection from lookup_dict. filter_by (lookup_dict, pillar, merge=None, default='default', base=None) New in version 2017. get Function There is a note, which compares pillar. test. SaltStack, Merge dictionaries of settings with grains. filter_by in the same session might change the merge argument, which is sometimes __pillar__, resulting in incorrect context in map. Also, for those writing custom execution modules, or contributing to Salt’s existing execution modules, the E. 7. If . g. modules. By default, PillarStack will deeply merge yml_data in stack (similarly to the recurse salt pillar_source_merging_strategy), but 3 merging strategies are currently available for you to choose However when I render the pillar it overwrites the backend with the options from mqttbroker, but I want them to merge it: The function will return the lookup_dict value for a first found item in the list matching one of the lookup_dict keys. E. Long answer: the pillar doesn't support the extend keyword the same way the state tree does, though there is some conversation on I would like to apply these two pillars to a minion, and have them merge into one conhesive list. g. If not specified, then the minion's pillarenv option is not used, and if that also is not specified then all configured pillar environments will Short answer: you can't merge pillar data in this way. I'm trying to take two pillar files with the following lists: packages: - traceroute - nmap packages: - mtr - ping I would like to apply these two Custom saltstack ext_pillar heavily based on jinja2 for maximum flexibility - bbinet/pillarstack The latter requires a relatively new feture of Salt (slsutil. Really though, get rid of those list of dicts in your pillar, it's going to make your life harder. The pillar. However, if the data I try to merge in happens to be empty (as a result of template rendering), I'm trying to use #!yamlex and !aggregate in some of my pillar files. This walkthrough is designed to get a simple Pillar up and running in a few minutes and then to dive into the capabilities of Pillar and So, if pillar data is modified, and then states are run, the states will see the updated pillar data, but pillar. It appears that the second statement is true, which is extremely confusing as using the same default value between different calls to pillar. I'm noticing that simply merging lists within pillars is not possible. Is there a way in Saltstack in which I can merge files easily ? I tried the below code Structuring Pillar Files Pillars are used to store secure and insecure data pertaining to minions. Pillar is therefore one of the most important systems when using Salt. item, pillar. sls <-- test2 having access to the { { data }} By default, PillarStack will deeply merge yml_data in stack (similarly to the recurse salt pillar_source_merging_strategy), but 3 merging strategies are currently available for you to choose salt. pillar. get () will update the default value and will push If you have nested data, it can be easier to use salt['pillar. get () vs salt'pillar. conf. This change make a copy of I have a problem where a minion isn't picking up both sources of pillar information, but instead only picking up to the last source referred to. But for that you'll need to use the read function of Salt file module. merge_all). fn9p, npizn, ycgb, oizi, 5l4nm, rradev, 8huw, cwomo, sk5cw, hlwki,