Encrypt/Remove kubeconfig secrets from build output about kubernetestask HOT 8 OPEN

I imagine there is a way to either:

1. Encrypt the contents of kube config since Base64 can easily be decoded: http://www.hashemian.com/tools/base64-encode-decode.php --> "Base64 decoding employs a reverse algorithm to yield the original content. While Base64 encoding alters the original content, it is not suitable as an encryption mechanism as it can be easily decoded to reveal the original content."
   or
2. Remove the output of the kube config from the build log.

from kubernetestask.

I don't know why. But I realised that if you have multiple lines of the parameter, vsts prints from the second line. VSTS doesn't print the first line. I should report to the VSTS production team about it.

The log is automatically out.
https://github.com/TsuyoshiUshio/KubernetesTask/blob/master/kubectl.ts#L31

from kubernetestask.

1.x is the same. Let's encode the kubecnfig file into Base64. Then it will be solved. See 5.1. Create an endopint on the README. :)

from kubernetestask.

Can I close this issue?

from kubernetestask.

from kubernetestask.

Not sure - somewhere here https://github.com/TsuyoshiUshio/KubernetesTask/blob/master/kubectl.ts I imagine with the kubeconfig.

from kubernetestask.

from kubernetestask.

@dtzar It seems automatically printout when I use this.

this.kubeconfig = tl.getEndpointAuthorizationParameter(this.endpoint, 'kubeconfig', true);

I can't avoid it. However, this line smells. I'll investigate it.

https://github.com/Microsoft/vsts-task-lib/blob/master/node/task.ts#L364

from kubernetestask.