-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add google_site_verification_web_resource #11624
Add google_site_verification_web_resource #11624
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @slevenick, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Errors
|
1 similar comment
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Errors
|
Tests analyticsTotal tests: 3781 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Tests analyticsTotal tests: 3898 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer.
|
Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_site_verification_web_resource" "primary" {
site {
identifier = # value needed
type = # value needed
}
verification_method = # value needed
}
|
Tests analyticsTotal tests: 3638 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_site_verification_web_resource" "primary" {
site {
identifier = # value needed
type = # value needed
}
verification_method = # value needed
}
|
Tests analyticsTotal tests: 3774 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_site_verification_web_resource" "primary" {
site {
identifier = # value needed
type = # value needed
}
verification_method = # value needed
}
|
Tests analyticsTotal tests: 3961 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
@slevenick This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
self_link: webResource/{{id}} | ||
create_url: webResource?verificationMethod={{verification_method}} | ||
delete_url: webResource/{{id}} | ||
id_format: '{{id}}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be webResource/{{id}}
? Usually we keep this in a selfLink-ish form so we can use .id from other resources. In this case that would probably never happen, but it would keep the ID formats standardized
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, changing id_format
results in a post-create read to /siteVerification/v1/webResource/webResource/{{id}}
.
FWIW I have a follow-up PR to add a fine grained resource to this resource, and the test resource looks like:
resource "google_site_verification_owner" "example" {
web_resource_id = google_site_verification_web_resource.example.id
email = "%{owner}"
}
It resolves OK 🤷
...rd_party/terraform/services/siteverification/resource_site_verification_web_resource_test.go
Outdated
Show resolved
Hide resolved
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_site_verification_web_resource" "primary" {
site {
identifier = # value needed
type = # value needed
}
verification_method = # value needed
}
|
Tests analyticsTotal tests: 3978 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Ah, that all makes sense! I did end up leaving in
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_site_verification_web_resource" "primary" {
site {
identifier = # value needed
type = # value needed
}
verification_method = # value needed
}
|
Tests analyticsTotal tests: 4034 Click here to see the affected service packages
Tests were added that are skipped in VCR:
Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
The adds support for the site verification API WebResource. It's step two out of three in implementing issue 5698. Step one was #10999 and step 3 will add the
owners
field as a fine grained resource attached to this resource.There's two basic ways to verify ownership of a site: creating a DNS record or modifying the site's content. I've included tests for both, but the former is disabled under VCR as it requires dynamically creating a real, resolvable DNS record as part of the test. I know we have
gcp.tfacc.hashicorptest.com
for use in other tests, but I couldn't find an example of creating records in that zone.Release Note Template for Downstream PRs (will be copied)