-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Open
Labels
ConfirmedSalt engineer has confirmed bug/feature - often including a MCVESalt engineer has confirmed bug/feature - often including a MCVERegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.bugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviorseverity-medium3rd level, incorrect or bad functionality, confusing and lacks a work around3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone
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 %}
pavel-z1
Metadata
Metadata
Assignees
Labels
ConfirmedSalt engineer has confirmed bug/feature - often including a MCVESalt engineer has confirmed bug/feature - often including a MCVERegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.bugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviorseverity-medium3rd level, incorrect or bad functionality, confusing and lacks a work around3rd level, incorrect or bad functionality, confusing and lacks a work around