[DOCS] Confusion over running custom modules in pillar
Open
Nobody has claimed this yet.
documentation
Pillar
severity-medium
time-estimate-single-day
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Message from @OrangeDog :
Just had someone confused about where things run. They needed to know that if you're using a custom module in a pillar you have to sync it to the master (with
salt-run saltutil.sync_all) not the minion (withsalt '*' saltutil.sync_all).
Not sure where documentation is best improved for that.
I'll think through the best place to communicate that idea.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the documentation for custom modules used in pillar and the saltutil.sync_all commands. Done means the relevant guidance clearly explains that pillar custom modules must be synced to the master, while minion modules use the minion command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100