Failed to load ext_pillar stack: no filter named 'unique' in 2018.3
Open
Nobody has claimed this yet.
bug
Confirmed
Regression
severity-medium
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description of Issue/Question
After upgrading to 2018.7 Saltstack doesn't know the Jinja filter 'unique' in the ext_pillar stack.
This worked ok before upgrading from 2017.7 and after downgrading back to 2017.7.
local:
Data failed to compile:
----------
Pillar failed to render with the following messages:
----------
Failed to load ext_pillar stack: no filter named 'unique'
Setup
snippet from external pillar stack *.yml file:
{% for app in a_dict | unique %}
{% endfor %}
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 with the external pillar stack YAML snippet using the unique filter and reproduce the rendering failure on Salt 2018.7, then compare it with 2017.7 where the snippet worked. Done means the same pillar stack renders successfully on the affected version or the compatibility problem is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100