Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure Elem is always either a *Schema or *Resource #929

Merged
merged 2 commits into from Jan 8, 2018

Conversation

jimmy-btn
Copy link
Contributor

This PR prepares this provider for hashicorp/terraform#17037, which will cause Provider.InternalValidate to reject schemas which assign invalid types (anything other than a *Schema or a *Resource) to the Elem field of a Schema.

This mostly addresses issues where the expected type for a Map is provided directly rather than wrapped in schema.Schema{}. Today this is a non-issue, but will cause problems in the future if we enforce type checking on Map types.

@danawillow
Copy link
Contributor

Thanks @jimmy-btn!

@danawillow danawillow merged commit a335265 into hashicorp:master Jan 8, 2018
@jimmy-btn jimmy-btn deleted the jimmy/fix-schemas branch January 8, 2018 20:49
jimmy-btn added a commit to jimmy-btn/terraform-provider-google that referenced this pull request Jan 12, 2018
rosbo pushed a commit that referenced this pull request Jan 12, 2018
modular-magician added a commit to modular-magician/terraform-provider-google that referenced this pull request Sep 27, 2019
Signed-off-by: Modular Magician <magic-modules@google.com>
@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants