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

Compute serviceattachment dcl #5444

Closed

Conversation

trodge
Copy link
Contributor

@trodge trodge commented Nov 12, 2021

Moved compute service attachment back to DCL implementation, fixing issues outlined in #5442

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)


@trodge trodge requested a review from rileykarson November 12, 2021 01:52
@google-cla google-cla bot added the cla: yes label Nov 12, 2021
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 9 files changed, 747 insertions(+), 997 deletions(-))
Terraform Beta: Diff ( 9 files changed, 747 insertions(+), 997 deletions(-))

@trodge
Copy link
Contributor Author

trodge commented Nov 12, 2021

/gcbrun

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 11 files changed, 751 insertions(+), 998 deletions(-))
Terraform Beta: Diff ( 12 files changed, 796 insertions(+), 998 deletions(-))

Copy link
Member

@rileykarson rileykarson left a comment

Choose a reason for hiding this comment

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

Thanks for making these changes @trodge!

I have some first-pass comments, inline- the documentation (inline) and a few remaining schema changes are the big things:

  • google_compute_service_attachment.consumer_accept_lists.connection_limit went from required -> optional
  • google_compute_service_attachment.enable_proxy_protocol went from required -> optional
  • google_compute_service_attachment.service_attachment_id does not appear to be returned by the API, so I'm unsure why it is supported by the DCL

Once those are resolved there's a couple pieces of tooling I'd like to run- I want to try out the release diff tester (ack that Scott already did, it's mostly for my own learning) and the schema diff tool.

@@ -3,7 +3,7 @@ module github.com/hashicorp/terraform-provider-google<%= "-" + version unless ve

require (
cloud.google.com/go/bigtable v1.10.1
github.com/GoogleCloudPlatform/declarative-resource-client-library v0.0.0-20211027225138-ef28ca390518
Copy link
Member

Choose a reason for hiding this comment

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

@ndmckinley can you verify that the newly-available fields in CloudBuild WorkerPool are intentional? It seems so, but I was surprised by the etag.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Are you referring to the fields that were added to beta in cl/408655015 ?

Copy link
Contributor

@nat-henderson nat-henderson Nov 15, 2021

Choose a reason for hiding this comment

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

Yeah - #5356 will add those to GA. They work in beta as of now! Would you like etag exluded? I don't mind either way, I forget what we decided on fingerprints. Could you comment on that PR with that?

@@ -25,7 +25,7 @@ func TestAccComputeServiceAttachment_serviceAttachmentBasicExampleUpdate(t *test
ResourceName: "google_compute_service_attachment.psc_ilb_service_attachment",
ImportState: true,
ImportStateVerify: true,
ImportStateVerifyIgnore: []string{"target_service", "region"},
ImportStateVerifyIgnore: []string{"target_service", "region", "nat_subnets.0"},
Copy link
Member

Choose a reason for hiding this comment

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

Why does this newly need to be set? Generally, having to set an ISVI value indicates that something's changed that will affect end users.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Without this the test still fails with:

    provider_test.go:278: ImportStateVerify attributes not equivalent. Difference is shown below. Top is actual, bottom is expected.
        
        (map[string]string) (len=1) {
         (string) (len=13) "nat_subnets.0": (string) (len=121) "https://www.googleapis.com/compute/beta/projects/tjr-dm-test-1/regions/us-west2/subnetworks/tf-test-psc-ilb-natn86tr1bw0e"
        }
        
        
        (map[string]string) (len=1) {
         (string) (len=13) "nat_subnets.0": (string) (len=81) "projects/tjr-dm-test-1/regions/us-west2/subnetworks/tf-test-psc-ilb-natn86tr1bw0e"
        }

nat_subnets Elem.DiffSuppressFunc is compareSelfLinkOrResourceName, so I'm fairly confident this is a problem that only occurs in testing.

@@ -0,0 +1,8 @@
- type: EXCLUDE
field: region
Copy link
Member

Choose a reason for hiding this comment

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

Ah, weird- the base DCL resource includes a (presumably output-only) region field but also a location field which maps to the region field in the API?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, this is the way KCC requested we name the fields. location corresponds to the URL parameter.

@@ -3,7 +3,7 @@ module github.com/hashicorp/terraform-provider-google<%= "-" + version unless ve

require (
cloud.google.com/go/bigtable v1.10.1
github.com/GoogleCloudPlatform/declarative-resource-client-library v0.0.0-20211027225138-ef28ca390518
github.com/GoogleCloudPlatform/declarative-resource-client-library v0.0.0-20211111235242-eee3ce55868a
Copy link
Member

Choose a reason for hiding this comment

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

Note, we'll want to handwrite documentation in the DCL and add reference links such as was done in #5325. That'll put the generated docs are at parity with the original ones. See the current diff:

image

Not sure on the process- you may have to look at @ndmckinley's history, and/or pester them to document it if it isn't intuitive.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

cl/409490555 should add the documentation to the DCL schema that the template needs to generate the page as it already exists.

@trodge
Copy link
Contributor Author

trodge commented Nov 12, 2021

Thanks for making these changes @trodge!

I have some first-pass comments, inline- the documentation (inline) and a few remaining schema changes are the big things:

  • google_compute_service_attachment.consumer_accept_lists.connection_limit went from required -> optional
  • google_compute_service_attachment.enable_proxy_protocol went from required -> optional
  • google_compute_service_attachment.service_attachment_id does not appear to be returned by the API, so I'm unsure why it is supported by the DCL

Once those are resolved there's a couple pieces of tooling I'd like to run- I want to try out the release diff tester (ack that Scott already did, it's mostly for my own learning) and the schema diff tool.

I have verified that the two fields which went from required to optional are in fact optional. I don't want to make them required in the DCL because this resource is already in KCC with the optional fields.

I meant to exclude service_attachment_id since it is not in the existing schema, but excluded the id field instead. I have fixed that in the latest commit.

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 11 files changed, 739 insertions(+), 998 deletions(-))
Terraform Beta: Diff ( 12 files changed, 784 insertions(+), 998 deletions(-))

@trodge trodge marked this pull request as ready for review November 12, 2021 23:46
@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccAssuredWorkloadsWorkload_BasicHandWritten|TestAccAssuredWorkloadsWorkload_FullHandWritten|TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeGlobalForwardingRule_privateServiceConnectGoogleApisExample|TestAccComputeInstanceFromMachineImage_basic|TestAccComputeInstanceFromMachineImage_overrideMetadataDotStartupScript|TestAccComputeInstanceFromMachineImage_diffProject|TestAccComputeRegionHealthCheck_tcp_update|TestAccComputeRegionHealthCheck_typeTransition|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccComputeServiceAttachment_BasicHandWritten|TestAccContainerCluster_withILBSubsetting|TestAccContainerCluster_regionalWithNodePool|TestAccContainerCluster_withNodePoolBasic|TestAccContainerCluster_withNodePoolResize|TestAccContainerCluster_withNodePoolUpdateVersion|TestAccContainerCluster_withNodePoolMultiple|TestAccContainerCluster_withNodePoolAutoscaling|TestAccContainerCluster_withNodePoolNodeConfig|TestAccContainerCluster_withEnableKubernetesAlpha|TestAccContainerNodePool_basic|TestAccContainerNodePool_basicWithClusterId|TestAccContainerNodePool_nodeLocations|TestAccContainerNodePool_maxPodsPerNode|TestAccContainerNodePool_withNodeConfig|TestAccContainerNodePool_withWorkloadIdentityConfig|TestAccContainerNodePool_withSandboxConfig|TestAccContainerNodePool_withKubeletConfig|TestAccContainerNodePool_withLinuxNodeConfig|TestAccContainerNodePool_withUpgradeSettings|TestAccContainerNodePool_withManagement|TestAccContainerNodePool_withInvalidUpgradeSettings|TestAccContainerNodePool_withGPU|TestAccContainerNodePool_withNodeConfigScopeAlias|TestAccContainerNodePool_autoscaling|TestAccContainerNodePool_regionalAutoscaling|TestAccContainerNodePool_resize|TestAccContainerNodePool_regionalClusters|TestAccContainerNodePool_version|TestAccContainerNodePool_012_ConfigModeAttr|TestAccContainerNodePool_EmptyGuestAccelerator|TestAccContainerNodePool_ephemeralStorageConfig|TestAccDataprocWorkflowTemplate_basic|TestAccEventarcTrigger_BasicHandWritten|TestAccServiceNetworkingPeeredDNSDomain_basic|TestAccMonitoringMonitoredProject_BasicMonitoredProject|TestAccNetworkServicesEdgeCacheOrigin_networkServicesEdgeCacheOriginBasicExample|TestAccNetworkServicesEdgeCacheOrigin_networkServicesEdgeCacheOriginAdvancedExample|TestAccNetworkServicesEdgeCacheService_networkServicesEdgeCacheServiceAdvancedExample|TestAccOrgPolicyPolicy_EnforcePolicy|TestAccOrgPolicyPolicy_FolderPolicy|TestAccOrgPolicyPolicy_ProjectPolicy|TestAccPrivatecaCertificateTemplate_BasicCertificateTemplate|TestAccSqlDatabaseInstance_withPrivateNetwork|TestAccSqlUser_postgresIAM You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=218087

@trodge trodge force-pushed the compute-serviceattachment-dcl branch from 71e222e to c47d39f Compare November 13, 2021 00:18
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 760 insertions(+), 1004 deletions(-))
Terraform Beta: Diff ( 17 files changed, 805 insertions(+), 1004 deletions(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccDatasourceGoogleServiceNetworkingPeeredDnsDomain_basic|TestAccAssuredWorkloadsWorkload_BasicHandWritten|TestAccAssuredWorkloadsWorkload_FullHandWritten|TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeGlobalForwardingRule_privateServiceConnectGoogleApisExample|TestAccComputeInstanceFromMachineImage_basic|TestAccComputeInstanceFromMachineImage_overrideMetadataDotStartupScript|TestAccComputeInstanceFromMachineImage_diffProject|TestAccComputeRegionHealthCheck_tcp_update|TestAccComputeRegionHealthCheck_typeTransition|TestAccComputeRegionHealthCheck_logConfigDisabled|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccComputeServiceAttachment_BasicHandWritten|TestAccContainerCluster_withILBSubsetting|TestAccContainerCluster_regionalWithNodePool|TestAccContainerCluster_withNodePoolBasic|TestAccContainerCluster_withNodePoolResize|TestAccContainerCluster_withNodePoolUpdateVersion|TestAccContainerCluster_withNodePoolAutoscaling|TestAccContainerCluster_withNodePoolMultiple|TestAccContainerCluster_withNodePoolNodeConfig|TestAccContainerCluster_withEnableKubernetesAlpha|TestAccContainerNodePool_basic|TestAccContainerNodePool_basicWithClusterId|TestAccContainerNodePool_nodeLocations|TestAccContainerNodePool_maxPodsPerNode|TestAccContainerNodePool_withNodeConfig|TestAccContainerNodePool_withWorkloadIdentityConfig|TestAccContainerNodePool_withSandboxConfig|TestAccContainerNodePool_withKubeletConfig|TestAccContainerNodePool_withLinuxNodeConfig|TestAccContainerNodePool_withUpgradeSettings|TestAccContainerNodePool_withInvalidUpgradeSettings|TestAccContainerNodePool_withGPU|TestAccContainerNodePool_withManagement|TestAccContainerNodePool_withNodeConfigScopeAlias|TestAccContainerNodePool_regionalAutoscaling|TestAccContainerNodePool_autoscaling|TestAccContainerNodePool_resize|TestAccContainerNodePool_regionalClusters|TestAccContainerNodePool_version|TestAccContainerNodePool_012_ConfigModeAttr|TestAccContainerNodePool_EmptyGuestAccelerator|TestAccContainerNodePool_ephemeralStorageConfig|TestAccDataprocWorkflowTemplate_basic|TestAccEventarcTrigger_BasicHandWritten|TestAccMonitoringMonitoredProject_BasicMonitoredProject|TestAccNetworkServicesEdgeCacheOrigin_networkServicesEdgeCacheOriginBasicExample|TestAccNetworkServicesEdgeCacheOrigin_networkServicesEdgeCacheOriginAdvancedExample|TestAccNetworkServicesEdgeCacheService_networkServicesEdgeCacheServiceAdvancedExample|TestAccOrgPolicyPolicy_EnforcePolicy|TestAccOrgPolicyPolicy_FolderPolicy|TestAccOrgPolicyPolicy_ProjectPolicy|TestAccPrivatecaCertificateTemplate_BasicCertificateTemplate|TestAccSqlDatabaseInstance_withPrivateNetwork|TestAccSqlUser_postgresIAM You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=218106

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 764 insertions(+), 1002 deletions(-))
Terraform Beta: Diff ( 17 files changed, 809 insertions(+), 1002 deletions(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeInstanceFromMachineImage_basic|TestAccComputeInstanceFromMachineImage_overrideMetadataDotStartupScript|TestAccComputeInstanceFromMachineImage_diffProject|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccContainerNodePool_withInvalidUpgradeSettings|TestAccEventarcTrigger_BasicHandWritten|TestAccSqlUser_postgresIAM You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=218308

@modular-magician
Copy link
Collaborator

Tests failed during RECORDING mode: TestAccEventarcTrigger_BasicHandWritten|TestAccComputeInstanceFromMachineImage_overrideMetadataDotStartupScript|TestAccComputeInstanceFromMachineImage_basic|TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeInstanceFromMachineImage_diffProject|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccContainerNodePool_withInvalidUpgradeSettings|TestAccSqlUser_postgresIAM Please fix these to complete your PR

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 891 insertions(+), 1051 deletions(-))
Terraform Beta: Diff ( 17 files changed, 936 insertions(+), 1051 deletions(-))

@nat-henderson
Copy link
Contributor

Nice - the new docs are just as good as the old ones, thanks for being diligent on that point.

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 889 insertions(+), 1049 deletions(-))
Terraform Beta: Diff ( 17 files changed, 934 insertions(+), 1049 deletions(-))

@rileykarson
Copy link
Member

Note: terraform-validator-test doesn't appear related

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccDatasourceGoogleServiceNetworkingPeeredDnsDomain_basic|TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccComputeServiceAttachment_ConsumerListsHandWritten|TestAccComputeServiceAttachment_BasicHandWritten|TestAccContainerNodePool_withInvalidUpgradeSettings|TestAccEventarcTrigger_BasicHandWritten|TestAccServiceNetworkingPeeredDNSDomain_basic|TestAccServiceDirectoryEndpoint_serviceDirectoryEndpointWithNetworkExample|TestAccSqlUser_postgresIAM You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=220259

@trodge
Copy link
Contributor Author

trodge commented Nov 19, 2021

/gcbrun

@trodge trodge force-pushed the compute-serviceattachment-dcl branch from 546d960 to 4f43639 Compare November 19, 2021 01:08
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 889 insertions(+), 1049 deletions(-))
Terraform Beta: Diff ( 17 files changed, 934 insertions(+), 1049 deletions(-))

@rileykarson
Copy link
Member

Ran both manual checks. I believe that we'll need to correct the last diff.go change as it causes a negative change in behaviour for some users, so it'd count as a backwards incompatibility:

DiffSuppressFunc for path region, was: compareSelfLinkOrResourceName is now

diff.go:

------------Diffing resource google_compute_service_attachment------------
Fields added in tpgtools: [psc_service_attachment_id]
Fields added in tpgtools: [connected_endpoints.psc_connection_id]
Required status different for path consumer_accept_lists.connection_limit, was: true is now false
Optional status different for path consumer_accept_lists.connection_limit, was: false is now true
DiffSuppressFunc for path consumer_accept_lists.project_id_or_num, was:  is now compareSelfLinkOrResourceName
DiffSuppressFunc for path consumer_reject_lists.elem, was:  is now compareSelfLinkOrResourceName
Required status different for path enable_proxy_protocol, was: true is now false
Optional status different for path enable_proxy_protocol, was: false is now true
DiffSuppressFunc for path project, was:  is now compareSelfLinkOrResourceName
DiffSuppressFunc for path region, was: compareSelfLinkOrResourceName is now
------------Done------------

RELEASE_DIFF=true:

$ RELEASE_DIFF=true make testacc TEST=./google-beta TESTARGS='-run=TestAccComputeServiceAttachment_'
==> Checking source code against gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 TF_SCHEMA_PANIC_ON_ERROR=1 go test ./google-beta -v -run=TestAccComputeServiceAttachment_ -timeout 240m -ldflags="-X=github.com/hashicorp/terraform-provider-google-beta/version.ProviderVersion=acc"
=== RUN   TestAccComputeServiceAttachment_BasicHandWritten
=== PAUSE TestAccComputeServiceAttachment_BasicHandWritten
=== RUN   TestAccComputeServiceAttachment_ConsumerListsHandWritten
=== PAUSE TestAccComputeServiceAttachment_ConsumerListsHandWritten
=== CONT  TestAccComputeServiceAttachment_BasicHandWritten
=== CONT  TestAccComputeServiceAttachment_ConsumerListsHandWritten
--- PASS: TestAccComputeServiceAttachment_ConsumerListsHandWritten (204.11s)
--- PASS: TestAccComputeServiceAttachment_BasicHandWritten (228.23s)
PASS
ok  	github.com/hashicorp/terraform-provider-google-beta/google-beta	229.410s

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 889 insertions(+), 1048 deletions(-))
Terraform Beta: Diff ( 17 files changed, 934 insertions(+), 1048 deletions(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccRedisInstanceDatasource_basic|TestAccCloudFunctionsFunction_vpcConnector|TestAccComputeBackendBucket_withCdnPolicy|TestAccComputeRegionNetworkEndpointGroup_regionNetworkEndpointGroupAppengineExample|TestAccContainerNodePool_withWorkloadIdentityConfig|TestAccEventarcTrigger_BasicHandWritten|TestAccServiceNetworkingPeeredDNSDomain_basic|TestAccRedisInstance_redisInstanceBasicExample|TestAccRedisInstance_redisInstanceFullExample|TestAccRedisInstance_update|TestAccRedisInstance_regionFromLocation|TestAccRedisInstance_redisInstanceAuthEnabled|TestAccRedisInstance_downgradeRedisVersion|TestAccSqlUser_postgresIAM You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=221745

Copy link
Member

@rileykarson rileykarson left a comment

Choose a reason for hiding this comment

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

Do you mind redoing the DCL upgrade to resolve conflicts? (upgrades are fairly annoying as they'll cause them fairly frequently)

@@ -166,7 +166,7 @@ func (l Link) Markdown() string {
}

func (r *Resource) fillLinksFromExtensionsMap(m map[string]interface{}) {
ref, ok := m["x-dcl-ref"].(map[string]interface{})
ref, ok := m["x-dcl-ref"].(map[interface{}]interface{})
Copy link
Member

Choose a reason for hiding this comment

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

What prompted this change? Given I can't see any key changes, these still seems to be strings all of the time.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With the previous line, ref is always an empty map and ok is always false and that's not the case with the new line. I suspect this has something to do with how the yaml is being read, but I'm not sure why the value is a map[interface{}]interface{} rather than a map[string]interface{}.

@trodge trodge force-pushed the compute-serviceattachment-dcl branch from e9ecf8c to f8be99c Compare November 23, 2021 00:41
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 16 files changed, 887 insertions(+), 1058 deletions(-))
Terraform Beta: Diff ( 16 files changed, 887 insertions(+), 1058 deletions(-))

@trodge trodge force-pushed the compute-serviceattachment-dcl branch from f8be99c to 4db6dbc Compare February 16, 2022 21:21
@trodge trodge closed this Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants