-
Notifications
You must be signed in to change notification settings - Fork 419
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
Default value for minion "master" parameter does not work #27
Comments
I am having the same issue. A temporary workaround is to provide an explicit master config for the minion template in the pillar:
It's hacky but works until we can get a proper fix. |
fwiw, this workaround doesn't seem to work for me anymore (
|
This should be resolved as of #179 |
Thanks @blast-hardcheese, if this is not resolved please comment on this issue and we can reopen it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the master is also being configured. The problem is this line in salt/files/minion:
If
pillars['salt']['minion']['master']
does not exist, it will trypillars['salt']['master']
, which of course is itself a dict.The text was updated successfully, but these errors were encountered: