Skip to content

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

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

wafrelka
Copy link
Contributor

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.

storage: fixed an issue where plans with a dependency on the `content` field in the `google_storage_bucket_object_content` data source could erroneously fail

@github-actions github-actions bot requested a review from slevenick January 24, 2025 15:48
Copy link

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.

@modular-magician modular-magician added awaiting-approval Pull requests that need reviewer's approval to run presubmit tests and removed awaiting-approval Pull requests that need reviewer's approval to run presubmit tests labels Jan 24, 2025
@slevenick
Copy link
Contributor

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?

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 60 insertions(+), 2 deletions(-))
google-beta provider: Diff ( 3 files changed, 60 insertions(+), 2 deletions(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 117
Passed tests: 106
Skipped tests: 9
Affected tests: 2

Click here to see the affected service packages
  • storage

Action taken

Found 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccDataSourceStorageBucketObjectContent_Issue15717
  • TestAccDataSourceStorageBucketObjectContent_Issue15717BackwardCompatibility

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

🟢 Tests passed during RECORDING mode:
TestAccDataSourceStorageBucketObjectContent_Issue15717 [Debug log]
TestAccDataSourceStorageBucketObjectContent_Issue15717BackwardCompatibility [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.


🟢 All tests passed!

View the build log or the debug log for each test

@wafrelka
Copy link
Contributor Author

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?

Yes.

According to the document, the field is supposed to be Computed and non-Optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot read the content attribute of the google_storage_bucket_object_content data source
3 participants