-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix bug in Pub/Sub Subscription avroConfig which was not sending empty configurations. #12108
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 bug in Pub/Sub Subscription avroConfig which was not sending empty configurations. #12108
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @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. |
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: 55 Click here to see the affected service packages
Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🟢 No issues found for passed tests after REPLAYING rerun. 🟢 All tests passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a new test or modify an existing one to explicitly specify avro_config {}
?
done! |
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: 56 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
@shuyama1 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test failed due to
resource_pubsub_subscription_test.go:364: Step 3/4 error: After applying this test step, the plan was not empty.
stdout:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# google_pubsub_subscription.foo will be updated in-place
~ resource "google_pubsub_subscription" "foo" {
id = "projects/ci-test-project-188019/subscriptions/tf-test-sub-qqpx9baf3m"
name = "tf-test-sub-qqpx9baf3m"
# (11 unchanged attributes hidden)
~ cloud_storage_config {
# (9 unchanged attributes hidden)
+ avro_config {}
}
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Please let me know if you need help debug the issue. https://googlecloudplatform.github.io/magic-modules/develop/diffs/, in case it helps
@shuyama1 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.
|
Tests analyticsTotal tests: 56 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test failed due to the same error, likely you'll need to add allow_empty_object: true
to avroConfig
field to allow sending avro_config {}
to the API.
@shuyama1 thanks for the pointer! What is the best way for me to trigger these tests? Running the tests following https://googlecloudplatform.github.io/magic-modules/develop/test/run-tests/ doesn't seem to be showing me the errors. |
You can probably follow the steps in https://googlecloudplatform.github.io/magic-modules/develop/test/run-tests/#run-automated-tests and run |
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: 56 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
Fixes: hashicorp/terraform-provider-google/issues/19658
Release Note Template for Downstream PRs (will be copied)