Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Where does all_saltenvs get list of environments from?

See original GitHub issue

Description of Issue/Question

Setup

Where does all_saltenvs get the list of environments from? When I use it, only base has access to the salt formula:

gitfs_remotes:
  - git@github.com:creativecommons/letsencrypt-formula.git:
    - all_saltenvs: master

When I look at /var/cache/salt/master/gitfs/envs.p only the base environment is listed. I have multiple environments defined under both file_roots and pillar_roots.

I seem to be able to accomplish what I think all_saltenvs is suppose to do with the following:

gitfs_saltenv:
  # Default/Production Environment
  - base:
    - ref: master
  # Development Environments
  - alden:
    - ref: master
  - kgodey:
    - ref: master
  - timidrobot:
    - ref: master

Versions Report

Salt Version:
           Salt: 2018.3.3
 
Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.5.3
      docker-py: Not Installed
          gitdb: 2.0.0
      gitpython: 2.1.1
          ioflo: Not Installed
         Jinja2: 2.9.4
        libgit2: 0.24.5
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.8
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: 0.24.2
         Python: 2.7.13 (default, Sep 26 2018, 18:42:22)
   python-gnupg: Not Installed
         PyYAML: 3.12
          PyZMQ: 16.0.2
           RAET: Not Installed
          smmap: 2.0.1
        timelib: Not Installed
        Tornado: 4.4.3
            ZMQ: 4.2.1
 
System Versions:
           dist: debian 9.6 
         locale: UTF-8
        machine: x86_64
        release: 4.9.0-8-amd64
         system: Linux
        version: debian 9.6

Issue Analytics

State:
Created 5 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

terminalmagecommented, Jan 16, 2019

Yeah, I’m sorry about that. I am the one that added that feature, and to be honest I hadn’t even considered a mixed environment containing both file_roots and gitfs_remotes. Oversight on my part, should have been documented better in the first place. Thanks for bringing this up, I’ll get the docs updated.

0reactions

terminalmagecommented, Jan 17, 2019

Documentation updated in https://github.com/saltstack/salt/pull/51231, closing this.

Top Results From Across the Web

Managing environments — conda 4.6.0 documentation

TIP: By default, environments are installed into the envs directory in your conda directory. Run conda create --help for information on specifying a...

List all virtualenv - Stack Overflow

This will grab all Python virtual environments present inside your home directory. For Mac Users, find works pretty good too find $HOME -name...

Master the basics of Conda environments in Python - YouTube

Master the basics of conda environments in Python: create environments (from command-line and YAML files), get information on them, ...

How to list packages in Conda Environment - YouTube

How to list packages in Conda Environment, how to list specific packages in Conda environment. Learn commands to be used in the Anaconda ......

salt.runners.fileserver - Salt Project Documentation

Executing this runner with no arguments will clear the cache for all enabled ... This function will return a dictionary showing a list...