gke-cluster-autopilot: add validation for release_channel input variable #1645
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.
This PR adds validation for the
release_channel
input variable. This is to align the code with the requirements for Autopilot clusters and to make the module more resilient to invalid input.Relevant Google Cloud docs:
The validation should not have any adverse effect on the rest of the codebase because the input variable name or type has not changed and the default value is provided. The default value I picked is the same value that the API uses if no value is specified. It is also the same value that is used by Cloud Console's form to create a new Autopilot cluster.
I also added a bit of context to the input variable's documentation string.
Checklist
I applicable, I acknowledge that I have:
terraform fmt
on all modified filestools/tfdoc.py