Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Failed to load ext_pillar stack: no filter named 'unique' in 2018.3 #46926

@morgana2313

Description

@morgana2313

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 %}

Metadata

Metadata

Assignees

No one assigned

    Labels

    ConfirmedSalt engineer has confirmed bug/feature - often including a MCVERegressionThe issue is a bug that breaks functionality known to work in previous releases.bugbroken, incorrect, or confusing behaviorseverity-medium3rd level, incorrect or bad functionality, confusing and lacks a work around

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions