Not all of the available configuration options are documented for master and minion configs. The following config values are undocumented in either of the "Configuring the Salt Master/Minion" docs.
Some of these values are in the master or minion sample conf files, but we should ensure that these config options are documented in both places.
The following config values are undocumented in the above referenced pages, beginning with the 2015.5 branch:
Configs new to the 2015.8 branch that need docs are:
Configs new to the 2016.3 branch that need docs are:
FYI @jacobhammons
In the 2015.8 branch, the gitfs_* and git_pillar_* config options are available in both the master and minion configs, however all of these configs are only documented in the "Configuring the Salt Master" doc, and not on the minion. This needs to be addressed as well. Refs #32397.
We should also write a test for this. It should be easy to just compare the keys of that config dict to a regex search of the master/minion config file.
extensive list, nice job @rallytime :+1:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
This is still relevant, though the list probably needs some updating.
Thank you for updating this issue. It is no longer marked as stale.
@barbaricyawps @ScriptAutomate this is in "Planning" vs. "Commit" for the Sodium project board, and tagging you 2 in case someone has time to look at this.
I have opened a new ticket related to this that's about getting the minion/master configs and docs synced up: #58112
The listed configuration values in this ticket, with unchecked boxes, still remain completely undocumented across both config files and the documentation files (except for event_match_type, which is in the master/minion conf files, but still needs to be in the documentation rst files in order to be checked off in this issue).
For the long-term, some form of automation needs to be in place to catch when new config values are created that are yet to be documented properly.
Please refer to the latest ticket with auditing for more configs that have been added to complete this work - closing.
Most helpful comment
We should also write a test for this. It should be easy to just compare the keys of that config dict to a regex search of the master/minion config file.