Change Details

SaltStack moved from OS-compliant packaging to "onedir packaging" to manage its own Python version. That means packages installed through pip are now only for Salt, provisioned in /opt/saltstack too. As such, here what happens on paas-docker: $ ls /opt/saltstack/salt/pypath/bin check_container_present check_http_200 docker-compose dotenv jsonschema normalizer wsdump.py $ docker-compose zsh: command not found: docker-compose We can see the two check files and docker-compose are both intended to be available for the whole userland, not only for Salt.

SaltStack moved from OS-compliant packaging to "onedir packaging" to manage its own Python version. That means packages installed through pip are now only for Salt, provisioned in /opt/saltstack too. As such, here what happens on paas-docker: $ ls /opt/saltstack/salt/pypath/bin check_container_present check_http_200 docker-compose dotenv jsonschema normalizer wsdump.py $ docker-compose zsh: command not found: docker-compose We can see the two check files and docker-compose are both intended to be available for the whole userland, not only for Salt. **Files and packages affected** * roles/paas-docker/devel/software.sls for docker-compose * roles/paas-docker/monitoring/init.sls for platform-checks

SaltStack moved from OS-compliant packaging to "onedir packaging" to manage its own Python version. That means packages installed through pip are now only for Salt, provisioned in /opt/saltstack too. As such, here what happens on paas-docker: $ ls /opt/saltstack/salt/pypath/bin check_container_present check_http_200 docker-compose dotenv jsonschema normalizer wsdump.py $ docker-compose zsh: command not found: docker-compose We can see the two check files and docker-compose are both intended to be available for the whole userland, not only for Salt. **Files and packages affected** * roles/paas-docker/devel/software.sls for docker-compose * roles/paas-docker/monitoring/init.sls for platform-checks