Open bernardhalas opened 5 months ago
I now see where the issue is, the provider configuration - after the subscription ID there is a new line
@bernardhalas, this is more of a user error, you have created a secret that has a whitespace (newline) at the end of the subscription ID (input manifest that you posted is ok syntactically).
To minimize this kind of error we could trim the whitespace when reading the secrets
I'll validate if the newline was coming from the azure provider secret. @Despire thanks for the hint.
any updates @bernardhalas ?
This can be reproduced for examply by executing:
echo "....secret...." | base64
to correctly base64 the secret without the implicit newline from echo:
echo -n "...secret..." | base64
Hi, this was indeed a problem on the side of a user. While using Claudie recently it appeared a few more times. I'd like to propose trimming the secret values, to ensure copy/paste whitespace and newline chars don't create errors which are difficult to fix.
Btw, in case someone comes across an error and suspects the issue being caused by a trailing newline char, this helps:
kubectl get secret name-of-secret -o go-template='
{{range $k,$v := .data}}{{printf "%s: " $k}}{{if not $v}}{{$v}}{{else}}{{$v | base64decode}}{{end}}{{"\n"}}{{end}}'
(ref)
Current Behaviour
Getting the following error:
Expected Behaviour
The input manifest should be processed successfully
Steps To Reproduce
Applying the manifest: