-
Notifications
You must be signed in to change notification settings - Fork 2.1k
workbench: fix workbench instance full test failing due to version being populated after resource creation #15182
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
workbench: fix workbench instance full test failing due to version being populated after resource creation #15182
Conversation
…resource creation
|
Hello! I am a robot. Tests will require approval from a repository maintainer to run. Googlers: For automatic test runs see go/terraform-auto-test-runs. @shuyama1, 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. |
|
@modular-magician reassign-reviewer @shuyama1 |
|
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.
|
Tests analyticsTotal tests: 25 Click here to see the affected service packages
🟢 All tests passed! View the build log |
|
Run tests on TC |
1ff501a
…ing populated after resource creation (GoogleCloudPlatform#15182)
…ing populated after resource creation (GoogleCloudPlatform#15182)
…ing populated after resource creation (GoogleCloudPlatform#15182)
…ing populated after resource creation (GoogleCloudPlatform#15182)
Fixes: hashicorp/terraform-provider-google#24315
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.