update hand written docs to reflect newly required fields #2682
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.
These should be the last of the nested objects.
Some assumptions I made along the way:
google_composer_environment.config.node_config.ip_allocation.use_ip_aliases
I made required, the other 4 seem to be grouped by 2 and conflict with each other, so I figured this was the safest one to make mandatory.I realized when adding
at_least_one_of
andexactly_one_of
to magic modules, it doesn't update anything in the docs. So I didn't update anything in the handwritten docs either (mostly for the time crunch, but with the excuse for consistency). I can update that there though, not sure if we want to document it on each field, or at the parent resource level.Release Note Template for Downstream PRs (will be copied)