Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Quiet is not #125

Open
hilari0n opened this issue Feb 25, 2022 · 0 comments
Open

Quiet is not #125

hilari0n opened this issue Feb 25, 2022 · 0 comments

Comments

@hilari0n
Copy link

Not all commands seem to respect the Quiet switch.
E.g. Invoke-DockerPull seems not to pass the Quiet switch to the Invoke-DockerCommand.
Also the docker process output is written using Write-Information -InformationAction 'Continue', which means, that the caller can't properly control the information stream. E.g. using Invoke-DockerPull -InformationAction Ignore will not work as expected (the information output will still be produced).
This means, that the only way of not having the Invoke-DockerCommand produce any output to the information channel, is by using the DOCKER_CI_QUIET_MODE environment variable, which is not very convenient, when you're writing a more complex automation/script where some output should be produced and some not.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant