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

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

[Ch3LL]

can you please share how you have your external pillar setup?

[morgana2313]

the master.conf contains:

ext_pillar:
  - stack:
      - [somepath]/stack.cfg
      - [somepath]/stack2.cfg

the stack2.cfg file contains:

somefile.yml

the somefile.yml contains:

        {% for app in stack.something | unique %}  # This 'unique' jinja filter gives an error in saltstack 2018.03??
          {{ app }}: {{ app }}
        {% endfor %}

[Ch3LL]

Thanks for adding teh configuration. Helped me to replicate it.

bisect shows: 494022d which is this PR.

ping @lorengordon any ideas here?

[lorengordon]

Basically the same problem fixed by #46744. The utils modules were all shifted around... The modules containing the jinja filters are not getting imported, and so the decorator is not getting called, which means the filters in utils modules that are not imported are not getting injected into the jinja env.

[morgana2313]

This problem still exists in Saltstack 2018.3.2

[Oloremo]

Having a similar problem with pillarstack and to_bool Jinja filter at 2018.3.3. Any updates?