Enhancement request: contents_pillar support for pkgrepo.managed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Sort of building on #55851 , so maybe you woud prefer to to broaden that original enhancement request as "Wider contents_pillar support throughout SaltStack" ? If its easy enough to refactor the codebase so that contents_pillar is available in any function where a fileserver salt:// can be used, I guess that would be the dream option !
Anyway, coming back to this specific request, looking at the docs, pkgrepo.managed has key_url and key_text but going by the docs neither have support for equivalent to contents_pillar.
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 reading the related discussion in #55851 and the pkgrepo.managed documentation for key_url and key_text. Clarify whether the goal is limited to contents_pillar support for those arguments or broader fileserver support throughout SaltStack. Done should be defined as an agreed scope with corresponding behavior and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100