Don't recreate google_container_cluster on master_auth change #1873
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.
I've used setMasterAuth to implement update of
username
andpassword
fields. Although there's no possibility to updateclient_certificate_config. issue_client_certificate
value and changing it will recreate cluster (no docs on that BTW. Also, I've stuck to forcing password input from a user and haven't implemented password autogeneration: not very useful feature and it will make the code more complex.Closes #1820