(maint) Hardening manifests and tasks
This PR aims to implement some changes that ensure no malformed commands are passed through to the system. Certain commands were left undivided as the commands did not get correctly interpreted.
Primarily, the commands targeted were the ones related to Open3 and exec.
docker::compose is a class
Breaking changes to this file WILL impact these 3 modules (exact match):
docker::install is a class
that may have no external impact to Forge modules.
docker::machine is a class
that may have no external impact to Forge modules.
docker::plugin is a type
that may have no external impact to Forge modules.
docker::registry is a type
Breaking changes to this file WILL impact these 2 modules (exact match):
docker::run is a type
Breaking changes to this file WILL impact these 9 modules (exact match):
Breaking changes to this file MAY impact these 22 modules (near match):
- cjtoolseram-drone
- autostructure-secure_docker
- KyleAnderson-consul
- puppet-consul
- puppet-grafana
- flyer-docker_cluster
- c0deaddict-gogs
- justin8-ghost
- jefferyb-kualicoeus
- pltraining-classroom_legacy
- pltraining-classroom
- bfraser-grafana
- factorit-grafana
- pltraining-dockeragent
- pltraining-puppetfactory
- puppetlabs-rancher
- nick-rancher
- prozeta-portauthority
- cristifalcas-docker_auth
- cristifalcas-docker_distribution
- cristifalcas-prometheus
- cristifalcas-kubernetes
docker::secrets is a type
that may have no external impact to Forge modules.
docker::services is a type
that may have no external impact to Forge modules.
docker::stack is a type
that may have no external impact to Forge modules.
docker::swarm is a type
Breaking changes to this file WILL impact these 2 modules (exact match):
This module is declared in 6 of 579 indexed public Puppetfiles.
These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.
Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.