-
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
Cloud Workstations - Workstation Cluster #7005
Cloud Workstations - Workstation Cluster #7005
Conversation
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Hello! I am a robot who works on Magic Modules PRs. I've detected that you're a community contributor. @ScottSuarez, a repository maintainer, has been assigned to assist you and help review your changes. ❓ First time contributing? Click here for more detailsYour assigned reviewer will help review your code by:
You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails. If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR hasn't generated any diffs, but I'll let you know if a future commit does. |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccComputeBackendService_withBackendAndMaxUtilization|TestAccComputeBackendService_withBackendAndIAP|TestAccComputeRegionAutoscaler_update|TestAccContainerCluster_withInvalidGatewayApiConfigChannel|TestAccComputeRegionPerInstanceConfig_update|TestAccComputeRegionAutoscaler_scalingSchedule|TestAccComputeRegionAutoscaler_scaleDownControl|TestAccComputeRegionAutoscaler_regionAutoscalerBasicExample|TestAccRegionInstanceGroupManager_stateful|TestAccRegionInstanceGroupManager_distributionPolicy|TestAccRegionInstanceGroupManager_autoHealingPolicies|TestAccComputeRegionBackendService_withBackendMultiNic|TestAccComputeRegionBackendService_withBackendInternalManaged|TestAccRegionInstanceGroupManager_versions|TestAccComputePerInstanceConfig_update|TestAccComputeRegionBackendService_withBackendInternal|TestAccRegionInstanceGroupManager_update|TestAccRegionInstanceGroupManager_targetSizeZero|TestAccRegionInstanceGroupManager_basic|TestAccComputeRegionBackendService_regionBackendServiceBalancingModeExample|TestAccComputeRegionAutoscaler_scaleInControl|TestAccInstanceGroupManager_waitForStatus|TestAccInstanceGroupManager_stateful|TestAccInstanceGroupManager_autoHealingPolicies|TestAccComputeGlobalForwardingRule_internalLoadBalancing|TestAccInstanceGroupManager_versions|TestAccInstanceGroupManager_update|TestAccInstanceGroupManager_targetSizeZero|TestAccInstanceGroupManager_basic|TestAccComputeGlobalForwardingRule_globalForwardingRuleInternalExample|TestAccComputeGlobalForwardingRule_externalHttpLbMigBackendCustomHeaderExample|TestAccDataSourceGoogleComputeInstanceGroup_fromIGM|TestAccComputeForwardingRule_forwardingRuleRegionalHttpXlbExample|TestAccLoggingBucketConfigProject_cmekSettings|TestAccComputeBackendService_withMaxConnections|TestAccComputeAutoscaler_scaleInControlFixed|TestAccComputeForwardingRule_internalHttpLbWithMigBackendExample|TestAccComputeAutoscaler_scaleInControl|TestAccComputeAutoscaler_scalingSchedule|TestAccComputeAutoscaler_multicondition|TestAccComputeAutoscaler_update|TestAccComputeAutoscaler_autoscalerBasicExample|TestAccComputeAutoscaler_autoscalerSingleInstanceExample|TestAccFirebaserulesRelease_BasicRelease|TestAccComputeForwardingRule_forwardingRuleHttpLbExample|TestAccComputeGlobalForwardingRule_externalTcpProxyLbMigBackendExample|TestAccComputeForwardingRule_internalTcpUdpLbWithMigBackendExample|TestAccComputeBackendService_withMaxConnectionsPerInstance|TestAccComputeAutoscaler_scaleDownControl|TestAccComputeBackendService_withBackend |
Tests passed during RECORDING mode: All tests passed |
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR hasn't generated any diffs, but I'll let you know if a future commit does. |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccBigtableAppProfile_bigtableAppProfileMulticlusterExample|TestAccContainerCluster_withInvalidGatewayApiConfigChannel|TestAccLoggingBucketConfigProject_cmekSettings |
Tests passed during RECORDING mode: All tests passed |
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR hasn't generated any diffs, but I'll let you know if a future commit does. |
Oops! It looks like you're using an unknown release-note type in your changelog entries:
Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR hasn't generated any diffs, but I'll let you know if a future commit does. |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccFirebaserulesRelease_BasicRelease|TestAccContainerCluster_withInvalidGatewayApiConfigChannel|TestAccLoggingBucketConfigProject_cmekSettings |
Tests passed during RECORDING mode: Tests failed during RECORDING mode: Please fix these to complete your PR |
@ScottSuarez, fixed the comments you put down. My assumption that the update in place wasn't working was incorrect. I just used the provider locally and the update only takes a few seconds. Can it be that because we use 2 different test configs (also 2 random suffixes or not?), it does recreate as part of the update test and therefor exceeds the timeout? Feel free to commit something in my branch btw. |
resource "google_compute_subnetwork" "default" { | ||
provider = google-beta | ||
name = "subnetwork-%{random_suffix}" | ||
ip_cidr_range = "10.0.0.0/24" | ||
region = "us-central1" | ||
network = google_compute_network.default.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.
The name of the subnetwork isn't matching up with generated name of the subnetwork in testAccWorkstationsWorkstationCluster_workstationClusterBasicExample
... This is forcing recreation here causing the google_workstations_workstation_cluster
to subsequently get recreated. Lets either align the names or encapsulate both configs (before and after) within this file explicitly.
modular-magician/terraform-provider-google-beta@auto-pr-7005-old..auto-pr-7005
#diff-38fbf90791
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.
Sharp.. thanks Scott
I pushed changes that should align the configurations |
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 ( 2 files changed, 251 insertions(+)) |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccContainerCluster_failedCreation|TestAccorkstationsWorkstationCluster_update |
It still failed for some reason, thanks for the fix @ScottSuarez |
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.
lgtm thanks for your patience and persistence!
Sweet! @ScottSuarez I'm going to immediately hop on the other Cloud Workstation resources. |
Co-authored-by: Scott Suarez <[email protected]> Closes hashicorp/terraform-provider-google#12763
I noticed a mistake here:
What do you recommend we do? Remove these in a major, or remove them now (might be a breaking change if we remove them now?) |
I don't think there's an issue with the provider, it's just that the documentation is a little misleading here. You marked those fields as outputs correctly and the resulting schema has those fields marked as Computed as we'd expect. The documentation misleading here because the We could address this by changing the template that generates these docs, e.g. to the idea below, but it'll have wide impacts and may need to be discussed by the maintainers about the correct approach:
👆 After saying all that, the tl;dr is I think it's our problem instead of yours! 😁 |
Thanks for elaborating @SarahFrench, you're right; it seems like the docs are misleading - I would think that they are arguments to pass. Anyhow, something we can fix in generating the docs correctly 👍🏼 |
Co-authored-by: Scott Suarez <[email protected]> Closes hashicorp/terraform-provider-google#12763
Closes #12763
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)