-
Notifications
You must be signed in to change notification settings - Fork 421
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
Can't create ext_pillar config with nested lists #383
Labels
Comments
For mongodb i use: salt:
master:
ext_pillar:
- mongo: "{ collection: salt_pillar }" Works for me (tm) |
@mrichar1 tried with the following config and it works:
|
Yep that's the solution I've gone with - will close this, thanks! |
This should be addressed if somebody else runs into this, they won't find this closed issue. |
For me, master_tops will actually take a dict, so the hack only seems to be necessary for ext_pillar: salt:
master:
ext_pillar:
- saltclass: "[ path: /srv/saltclass ]"
master_tops:
saltclass:
path: /srv/saltclass
|
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to add the following config via this formula:
However the logic in the formula doesn't seem to have a path that can output this style of config: https://github.com/saltstack-formulas/salt-formula/blob/master/salt/files/master.d/f_defaults.conf#L1180
It's probably possible to extend the logic to handle it, but given how horribly complex it already is, is there a reason not to just insert literal yaml in this kind of config, rather than trying to unpack yaml and rebuild it again?
Something like (untested):
The text was updated successfully, but these errors were encountered: