fix(schema): Correct schema definitions #52
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
355a013 to
ca5c36a
Compare
Various schemas have been updated for correctness. Notably, although an incorrect Elem definition for custom_headers is provided, this field still does not work as is due to a limitation in Terraform. Maps of mixed types are not possible to use or define, and therefore a workaround would be required to implement this field. This more correct definition is here in case this Terraform behavior changes in the future.
ca5c36a to
a2e0e41
Compare
william20111
approved these changes
May 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Various schemas have been updated for correctness.
Notably, although an incorrect Elem definition for custom_headers is
provided, this field still does not work as is due to a limitation in
Terraform. Maps of mixed types are not possible to use or define, and
therefore a workaround would be required to implement this field. This
more correct definition is here in case this Terraform behavior changes
in the future.