-
Notifications
You must be signed in to change notification settings - Fork 100
Document Octopus.Action.Kubernetes.VerboseOutput variable for CLI tool logging #2993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
|
||
| Setting the Octopus variable `Octopus.Action.Kubernetes.OutputKubeConfig` to `True` for any deployment or runbook using a Kubernetes target will cause the generated kube config file to be printed into the logs (with passwords masked). This can be used to verify the configuration file used to connect to the Kubernetes cluster. | ||
|
|
||
| Setting the Octopus variable `Octopus.Action.Kubernetes.VerboseOutput` to `True` will cause successful output from Kubernetes CLI tools (`kubectl`, `helm`, `aws`, `az`, `gcloud`, etc.) to be logged at the Info level instead of Verbose. This is useful when debugging deployments to see the full output of these tools without needing to enable verbose logging for the entire deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could mention the default logging level if this flag is not set or false? For example, do we only log errors if VerboseOutput is False?
|
|
||
| `Octopus.Action.Kubernetes.VerboseOutput` | ||
|
|
||
| Set to `True` to log successful output from Kubernetes CLI tools (`kubectl`, `helm`, `aws`, `az`, `gcloud`, etc.) at the Info level instead of Verbose. This is useful when debugging deployments to see the full output of these tools without needing to enable verbose logging for the entire deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could mention the default logging level if this flag is not set or false? For example, do we only log errors if VerboseOutput is False?
|
@HuyPhanNguyen I've fixed the Markdown Lint errors. It would be useful to explain what logging level is set if the flag isn't passed, or is |
Add
Octopus.Action.Kubernetes.VerboseOutputvariable to log CLI tool output at Info level for Kubernetes stepsOctopusDeploy/Issues#9786