saltstack / saltstack/salt

[FEATURE REQUEST] pillar:// as a way of ambiguously target pillar files regardless of filesystem.

Open
#58,346 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Is your feature request related to a problem? Please describe.
I know this won't be an easy feature to create so just going to start out with the basic's sometimes it is difficult to do jinja or python from within pillar cause as soon as you need to access another file you need to know how the file is loaded from what file system. if we had a way of accessing the file regardless of if we are using gitfs or other methods. that disambiguates the pillar filesystem for tools like slsutil.renderer.

Describe the solution you'd like
a new keyword kind of like salt:// that says this is in the pillar filesystem. such as pillar:// it should only be accessible from within pillar templates.

Describe alternatives you've considered
using salt:// to "smartly" decide where the file is. might be a better option but can be confusing to someone coming in without a clear idea that salt:// normally means the salt fileserver.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how slsutil.renderer resolves salt:// references from pillar templates and how those references select a filesystem. Define what pillar:// should resolve to across supported filesystems and restrict it to pillar templates; done means the behavior is implemented and verified for the requested use case.

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
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.