Repository navigation
Behaviour change: env values are masked in task output by default
Container env values no longer show up in task output. Before this release, community.docker.docker_container printed them in --diff output and in -v / -vvv runs, so a secret passed through env could end up in terminal scrollback, CI logs or log shipping.
The role now runs the module through a new action plugin, netresearch_docker_container (@tripleawwy in #38). It masks every env value in:
--diff(changed values are marked(changed)on the new side, since both sides look the same once masked)-v(thecontainer.Config.Envdump) and-vvv(invocation.module_args.env)- check mode
- error text such as
msg,stderrandstdout, for values of 8 or more characters
Playbooks keep working unchanged. If you relied on seeing env values in the output, opt out:
netresearch_docker_containers_redact_env: falseturns masking off for the whole roleredact_env: true|falseon a container overrides the role default for that containerenv_visible: [NAME, ...]on a container keeps the listed env names readable while the rest stay masked; a name that is not inenvfails the task (unlessstate: absent)
The README has a new "Env values in task output" section with the details and the known limits: values shorter than 8 characters or coming only from env_file are masked by name only in error text, and labels, command and mounts are not masked.
Other changes
- Molecule scenario definitions fixed for current Molecule, plus a new
env-redactscenario and CI job that fails when a canary env value appears in the output (@tripleawwy, #38) - CI and repository maintenance (@CybotTM): Dependabot configuration removed (#34), secret scan called as
betterleaks.yml(#35) with reduced permissions (#36), Renovate extends the org preset (#37)
Full Changelog: v1.8.0...v1.9.0