Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pillarenv not working #53477

Open
achinayoungwaubonsee opened this issue Jun 13, 2019 · 3 comments

Comments

@achinayoungwaubonsee
Copy link

commented Jun 13, 2019

Description of Issue

Trying to configure a separate dev salt/pillar environment. However, passing pillarenv=dev on the command-line doesn't return pillar values from the pillar dev directory.

Setup

# salt-run config.get file_roots
base:
    - /usr/share/susemanager/salt
    - /usr/share/susemanager/formulas/states
    - /srv/susemanager/salt
    - /srv/salt
dev:
    - /srv/salt-dev
# salt-run config.get pillar_roots
base:
    - /srv/pillar
dev:
    - /srv/pillar-dev

# cat /srv/pillar/top.sls
base:
  '*':
    - noop
# cat /srv/pillar/noop.sls
value: b

# cat /srv/pillar-dev/top.sls
dev:
  '*':
    - noop
# cat /srv/pillar-dev/noop.sls
value: a

Steps to Reproduce Issue

# salt <id> pillar.item value pillarenv=dev
<id>:
    ----------
    value:
        b
# salt <id> pillar.item value pillarenv=base
<id>:
    ----------
    value:
        b

I would expect the first result to be a.

Versions Report

# salt --versions-report
Salt Version:
           Salt: 2018.3.0

Dependency Versions:
           cffi: 1.5.2
       cherrypy: 3.6.0
       dateutil: 2.4.2
      docker-py: Not Installed
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: 0.24.0
        libnacl: Not Installed
       M2Crypto: 0.29.0
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: 2.10
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: 0.24.0
         Python: 2.7.13 (default, Jan 11 2017, 10:56:06) [GCC]
   python-gnupg: Not Installed
         PyYAML: 3.12
          PyZMQ: 14.0.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.0.4

System Versions:
           dist: SuSE 12 x86_64
         locale: UTF-8
        machine: x86_64
        release: 4.12.14-95.16-default
         system: Linux
        version: SUSE Linux Enterprise Server  12 x86_64
@Ch3LL

This comment has been minimized.

Copy link
Contributor

commented Jun 14, 2019

I was able to confirm this behavior. But I also tested the lastest 2018.3 version 2018.3.4 and its working:

[root@96abe8f24795 testing]# salt '*' pillar.item value pillarenv=dev
96abe8f24795:
    ----------
    value:
        a
[root@96abe8f24795 testing]# salt '*' pillar.item value pillarenv=base
96abe8f24795:
    ----------
    value:
        b
[root@96abe8f24795 testing]# salt --version
salt 2018.3.4 (Oxygen)
@achinayoungwaubonsee

This comment has been minimized.

Copy link
Author

commented Jun 14, 2019

So then we should just close this as it's specific to our version?

@Ch3LL

This comment has been minimized.

Copy link
Contributor

commented Jun 17, 2019

yep we can close if your okay with this as it is fixed in the newer version. If you want to verify this before we close that would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.