fix: azuredevops_serviceendpoint_kubernetes
kubeconfig update failure and plugin crash
#638
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.
All Submissions:
What about the current behavior has changed?
Terraform now prevents showing sensitive data to log/console. The encoding with
bcrypt
of a kubeconfig file will often leads to no diff detected sincebcrypt
has a limit of only 72 bytes.As for #619, this removes the hash attribut.
I also included a fix a plugin crash when the
cluster_context
attribut was not specified.Issue Number: #613, #635
Does this introduce a change to
go.mod
,go.sum
orvendor/
?Does this introduce a breaking change?
Remove the hash will not be a breaking change and no diff is shown on plan or apply
Any relevant logs, error output, etc?
Plugin crash log when the
cluster_context
attribut was not specified:Other information