Graduating Cloud Workstations resources from "google-beta" to "google" provider#16713
Conversation
5de5150 to
c856a40
Compare
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @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. |
c856a40 to
af51a91
Compare
… to google provider.
af51a91 to
701b829
Compare
|
@trodge This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
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.
Multiple resources addedThis PR adds multiple new resources: |
Non-exercised tests🔴 Tests were added that are GA-only additions and require manual runs:
Tests analyticsTotal tests: 38 Click here to see the affected service packages
🟢 All tests passed! View the build log |
|
Could a maintainer add the label "override-multiple-resources" ? This PR is graduating 3 deeply connected resources from google-beta to google provider. It is not adding any resources to the codebase. Between the dependency chain, tests and the actual usage I don't think splitting up the CL to graduate one resource at a time is feasible. |
c5f4fe1
This includes resources for: "Workstation", "WorkstationConfig", and "WorkstationCluster".
Updates API endpoint to point to "v1" endpoint instead of "v1beta" endpoint.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.