Check whether provided base64 encoded data in KubeConfig is valid #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi again, thanks for the quick response on my last PR.
I came across another minor thing, while testing i inadvertently used an invalid base64 encoded certificate in my kube config. This did not result in a clear error message, as the
file_put_contents
function successfully wrote the boolfalse
as contents of the certificate.pem file. Later down the line this resulted in an less obvious Curl error 58.Therefore i added a check to make sure it at least was able to decoding something from the base64 contents.