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

helper/schema: validate subresources more effectively #997

Merged
merged 1 commit into from
Feb 18, 2015

Conversation

mitchellh
Copy link
Contributor

Fixes #740

Our validator wasn't picking up unknown keys in subresources. This fixes that. I also added an extra test for completion but it wasn't failing to begin with.

@@ -2500,7 +2500,7 @@ func TestSchemaMap_Validate(t *testing.T) {
},
},

// Good, because the var is not set and that error will come elsewhere
// #1 Good, because the var is not set and that error will come elsewhere
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noooooo shoulda just made them K/V with test names if you were already touching everything. 😀

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha it was a lot easier to just do this.

@phinze
Copy link
Contributor

phinze commented Feb 18, 2015

LGTM!

mitchellh added a commit that referenced this pull request Feb 18, 2015
helper/schema: validate subresources more effectively
@mitchellh mitchellh merged commit a91eaa1 into master Feb 18, 2015
@mitchellh mitchellh deleted the b-validate-subresource branch February 18, 2015 18:23
@ghost
Copy link

ghost commented May 4, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 4, 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.

AWS VPC Security Group loses all ingresses
2 participants