-
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 network attachment to gce instance #8829
Add network attachment to gce instance #8829
Conversation
…tachment merge from upstream/main
…tachment update merge from upstream/main
…tachment sync merge from upstream/main
…tachment sync merge from upstream/main
…tachment sync merge from upstream/main
…tachment sync merge upstream/main
…nt-to-gce-instance sync merge from upstream/main
…nt-to-gce-instance sync merge from upstream/main
…nt-to-gce-instance sync merge from upstream/main
Hello! I am a robot. It looks like you are a: Community Contributor @trodge, 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. |
…nt-to-gce-instance sync merge from upstream/main
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. Terraform Beta: Diff ( 2 files changed, 285 insertions(+)) Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
network_interface {
network_attachment = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
network_interface {
network_attachment = # value needed
}
}
|
Tests analyticsTotal tests: 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 testsTestAccComputeInstance_networkAttachmentUpdate|TestAccComputeInstance_NetworkAttachment |
|
…nt-to-gce-instance sync merge from upstream/main
Tests are failing with the following error:
|
mmv1/third_party/terraform/services/compute/resource_compute_instance_test.go.erb
Outdated
Show resolved
Hide resolved
mmv1/third_party/terraform/services/compute/resource_compute_instance_test.go.erb
Outdated
Show resolved
Hide resolved
…nt-to-gce-instance sync merge from upstream/main
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. Terraform GA: Diff ( 1 file changed, 11 insertions(+), 8 deletions(-)) Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
network_interface {
network_attachment = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
network_interface {
network_attachment = # value needed
}
}
|
Tests analyticsTotal tests: 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 testsTestAccBigQueryDataTable_bigtable|TestAccBigtableAppProfile_bigtableAppProfileAnyclusterExample|TestAccBigtableAppProfile_bigtableAppProfileSingleclusterExample|TestAccBigtableAppProfile_bigtableAppProfileMulticlusterExample|TestAccComputeInstance_networkAttachmentUpdate|TestAccComputeInstance_NetworkAttachment |
Rerun these tests in REPLAYING mode to catch issues
|
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. Terraform GA: Diff ( 1 file changed, 11 insertions(+), 8 deletions(-)) Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_instance_from_machine_image" "primary" {
network_interface {
network_attachment = # value needed
}
}
Resource: resource "google_compute_instance_from_template" "primary" {
network_interface {
network_attachment = # value needed
}
}
|
Tests analyticsTotal tests: 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 testsTestAccComputeInstance_NetworkAttachmentUpdate |
Rerun these tests in REPLAYING mode to catch issues
|
* first draft for new Network Attachment resource * updated NetworkAttachment specification file * added usage example for Network Attachment with GCE Instance * verified attributes and descriptions * enhanced network attachment examples * adding network attachment field to compute instance network interface * added network attachment specification to yaml file * added integration tests * fixing minor typo * fixed typo * fixed typo * fixed tf config * fixed typo * fixed network attachment simple test * updated instance resource documentation * removed bad logic network attachment validation * fixed tests and field specification for network attachment
This PR enables support for network attachment at the gce instance network interfaces
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
in the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)