Add terraform support for InterconnectGroup and InterconnectAttachmentGroup resources#13870
Conversation
|
Hello! I am a robot. Tests will require approval from a repository maintainer to run. Googlers: see go/terraform-auto-test-runs to set up automatic test runs. @SirGitsalot, 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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_interconnect_attachment_group" "primary" {
attachments {
attachment = # value needed
key_attachment = # value needed
}
configured {
availability_sla {
effective_sla = # value needed
intended_sla_blockers {
attachments = # value needed
blocker_type = # value needed
documentation_link = # value needed
explanation = # value needed
metros = # value needed
regions = # value needed
zones = # value needed
}
}
}
interconnect_group = # value needed
logical_structure {
regions {
metros {
facilities {
facility = # value needed
zones {
attachment = # value needed
zone = # value needed
}
}
metro = # value needed
}
region = # value needed
}
}
}
Resource: resource "google_compute_interconnect_group" "primary" {
configured {
topology_capability {
intended_capability_blockers {
blocker_type = # value needed
documentation_link = # value needed
explanation = # value needed
facilities = # value needed
interconnects = # value needed
metros = # value needed
zones = # value needed
}
supported_sla = # value needed
}
}
interconnects {
interconnect = # value needed
key_interconnect = # value needed
}
physical_structure {
metros {
facilities {
facility = # value needed
zones {
interconnects = # value needed
zone = # value needed
}
}
metro = # value needed
}
}
}
|
Tests analyticsTotal tests: 1191 Click here to see the affected service packages
Action takenFound 6 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🟢 Tests passed during RECORDING mode: 🟢 No issues found for passed tests after REPLAYING rerun. 🟢 All tests passed! |
|
Hi @SirGitsalot ! Please help review this PR. Thanks! |
|
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_compute_interconnect_attachment_group" "primary" {
attachments {
attachment = # value needed
key_attachment = # value needed
}
configured {
availability_sla {
effective_sla = # value needed
intended_sla_blockers {
attachments = # value needed
blocker_type = # value needed
documentation_link = # value needed
explanation = # value needed
metros = # value needed
regions = # value needed
zones = # value needed
}
}
}
interconnect_group = # value needed
logical_structure {
regions {
metros {
facilities {
facility = # value needed
zones {
attachment = # value needed
zone = # value needed
}
}
metro = # value needed
}
region = # value needed
}
}
}
Resource: resource "google_compute_interconnect_group" "primary" {
configured {
topology_capability {
intended_capability_blockers {
blocker_type = # value needed
documentation_link = # value needed
explanation = # value needed
facilities = # value needed
interconnects = # value needed
metros = # value needed
zones = # value needed
}
supported_sla = # value needed
}
}
interconnects {
interconnect = # value needed
key_interconnect = # value needed
}
physical_structure {
metros {
facilities {
facility = # value needed
zones {
interconnects = # value needed
zone = # value needed
}
}
metro = # value needed
}
}
}
|
Tests analyticsTotal tests: 1193 Click here to see the affected service packages
🟢 All tests passed! View the build log |
|
@SirGitsalot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
Hi @SirGitsalot Looks like rebasing didn't fix the issue. PTAL |
|
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_compute_interconnect_attachment_group" "primary" {
attachments {
attachment = # value needed
name = # value needed
}
interconnect_group = # value needed
}
Resource: resource "google_compute_interconnect_group" "primary" {
interconnects {
interconnect = # value needed
name = # value needed
}
}
Multiple resources addedThis PR adds multiple new resources: |
Tests analyticsTotal tests: 1215 Click here to see the affected service packages
Found 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 during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
|
@SirGitsalot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
SirGitsalot
left a comment
There was a problem hiding this comment.
Ran the tests against the TeamCity upstreams to filter out the noise from all of the various passes on the PR and they passed. The two VCR failures are a known, unrelated issue.
5c634d7
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.