-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Mark content
in storage object content data source as computed
#12857
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
Mark content
in storage object content data source as computed
#12857
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @slevenick, 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. |
Odd, so the issue here is that the field should be Computed and not Optional, but due to it being marked as Optional in the past we have to keep it that way? |
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: 117 Click here to see the affected service packages
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 tests
|
Yes. According to the document, the field is supposed to be Computed and non-Optional. |
Fixes hashicorp/terraform-provider-google#15717 in a backward-compatible manner.
The bug was once fixed in #10778, but it is reverted due to backward incompatibility.
This pull request retries to fix the bug without affecting to existing configuration.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.