Description
Describe your feature request here
A Service Connection of type Kubernetes has an authorization parameter clusterContext. This parameter is then masked I believe cause it is not part of the exclusion list here
However this can result in the masking of this within the pipeline logs, which hides some useful metadata on runs as generally the context can be taken as the same name as the cluster. I don't believe the context is sensitive in any form so would be great if this can be added to the exclusion list.
e.g.
Cluster Name: my-test-cluster
Kube Config Context: my-test-cluster
Service Connection authorization parameter
"authorization": {
"parameters": {
"clusterContext": "my-test-cluster"
},
"scheme": "Kubernetes"
},
When using the cluster name above as say a parameter in a template then it gets masked in the logs. In our case we are logging out a message via LogIssue task command
Results in
##[error]{"environment": "dev", "cluster": "***", "region": "somewhere", "namespace": "dev", "status": "Failed", "type": "live"}