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

Add IAM to DNS managed Zone, change DNS name for failed tests in quic… #6918

Merged
merged 1 commit into from
Dec 20, 2022

Conversation

hao-nan-li
Copy link
Contributor

…kstart.tf

Add IAM to DNS managed Zone, change DNS name for failed tests in quickstartExample

If this PR is for Terraform, I acknowledge that I have:

  • Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
  • Generated Terraform, and ran make test and make lint to ensure it passes unit and linter tests.
  • Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
  • Ran relevant acceptance tests (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
  • Read the Release Notes Guide before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

Add IAM to DNS managed Zone, change DNS name for failed tests in quickstartExample

@@ -38,7 +38,7 @@ resource "google_compute_firewall" "default" {
# to create a DNS zone
resource "google_dns_managed_zone" "<%= ctx[:primary_resource_id] %>" {
name = "<%= ctx[:vars]['example_zone_googlecloudexample'] %>"
dns_name = "googlecloudexample.com."
dns_name = "googlecloudexample.net."
Copy link
Member

Choose a reason for hiding this comment

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

what happened to the googlecloudexample.com DNS zone? Can we recover it rather than changing the one we're testing against?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Riley agreed with changing the domain name. It doesn't seem easy to own domains to run tests.

Copy link
Member

@melinath melinath Dec 6, 2022

Choose a reason for hiding this comment

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

What will the impact of this change be? For example, will this test end up purchasing the DNS?

Copy link
Contributor Author

@hao-nan-li hao-nan-li Dec 6, 2022

Choose a reason for hiding this comment

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

I don't think we purchase the DNS with this test. According to the test, it looks like a compute instance will be created as a web server, reachable through port 80. Finally an IP address will be registered under the DNS.

Since there is a deletion at the end of the test, the IP and the port will be used for about 2-5 minutes (Tested locally).

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 5 files changed, 805 insertions(+), 3 deletions(-))
Terraform Beta: Diff ( 5 files changed, 805 insertions(+), 3 deletions(-))
TF Validator: Diff ( 5 files changed, 325 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 1 insertion(+), 1 deletion(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2332
Passed tests 2082
Skipped tests: 244
Failed tests: 6

Action taken

Triggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed tests
TestAccFirebaserulesRelease_BasicRelease|TestAccDNSManagedZoneIamPolicyGenerated|TestAccDNSManagedZoneIamMemberGenerated|TestAccDNSManagedZoneIamBindingGenerated|TestAccDNSManagedZone_dnsManagedZoneQuickstartExample|TestAccLoggingBucketConfigProject_cmekSettings

@modular-magician
Copy link
Collaborator

Tests passed during RECORDING mode:
TestAccFirebaserulesRelease_BasicRelease[Debug log]
TestAccDNSManagedZoneIamPolicyGenerated[Debug log]
TestAccDNSManagedZoneIamMemberGenerated[Debug log]
TestAccDNSManagedZoneIamBindingGenerated[Debug log]
TestAccDNSManagedZone_dnsManagedZoneQuickstartExample[Debug log]
TestAccLoggingBucketConfigProject_cmekSettings[Debug log]

All tests passed
View the build log or the debug log for each test

@DrFaust92
Copy link
Contributor

hao-nan-li melinath any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants