Skip to content
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

fix: Allow Pub/Sub Topic update to remove schema settings #11038

Conversation

kamalaboulhosn
Copy link
Contributor

Remove default_from_api from Pub/Sub Topic schemaSettings so that schema settings can be removed from a topic. Fixes hashicorp/terraform-provider-google#15925.

Release Note Template for Downstream PRs (will be copied)

pubsub: Allow `schema_settings` of `google_pubsub_topic` to be removed

Copy link

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@roaks3, 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
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 ( 2 files changed, 12 insertions(+), 2 deletions(-))
google-beta provider: Diff ( 2 files changed, 12 insertions(+), 2 deletions(-))

Breaking Change(s) Detected

The following breaking change(s) were detected within your pull request.

  • Field schema_settings transitioned from optional+computed to optional google_pubsub_topic - reference

If you believe this detection to be incorrect please raise the concern with your reviewer.
If you intend to make this change you will need to wait for a major release window.
An override-breaking-change label can be added to allow merging.

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 49
Passed tests: 47
Skipped tests: 1
Affected tests: 1

Click here to see the affected service packages
  • pubsub

Action taken

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

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccPubsubTopic_schema[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$


$\textcolor{green}{\textsf{All tests passed!}}$
View the build log or the debug log for each test

Copy link

@roaks3 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label disable-review-reminders to disable these notifications.

Copy link
Contributor

@roaks3 roaks3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I think we might still want an entry in the upgrade guide for this. Something like "a default value is not longer provided for schema_settings, instead an empty value means the setting should be cleared"?

@github-actions github-actions bot requested a review from roaks3 July 2, 2024 11:30
@kamalaboulhosn
Copy link
Contributor Author

@roaks3 Added an entry as suggested.

@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, 18 insertions(+), 2 deletions(-))
google-beta provider: Diff ( 3 files changed, 18 insertions(+), 2 deletions(-))

Breaking Change(s) Detected

The following breaking change(s) were detected within your pull request.

  • Field schema_settings transitioned from optional+computed to optional google_pubsub_topic - reference

If you believe this detection to be incorrect please raise the concern with your reviewer.
If you intend to make this change you will need to wait for a major release window.
An override-breaking-change label can be added to allow merging.

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 49
Passed tests: 48
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log

@roaks3 roaks3 added the override-breaking-change Allows a potential breaking change to be merged label Jul 2, 2024
@roaks3 roaks3 merged commit 0c8818e into GoogleCloudPlatform:FEATURE-BRANCH-major-release-6.0.0 Jul 2, 2024
12 of 13 checks passed
c2thorn pushed a commit to c2thorn/magic-modules that referenced this pull request Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
override-breaking-change Allows a potential breaking change to be merged service/pubsub
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants