-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Allow PSC Service Attachment to update target_service as a mutable update #16221
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
Allow PSC Service Attachment to update target_service as a mutable update #16221
Conversation
|
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. @NickElliot, 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: 1330 Click here to see the affected service packages
Action takenFound 3 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. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
NickElliot
left a comment
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 is failing with the following:
resource_compute_service_attachment_test.go:134: Step 1/3 error: Error running pre-apply refresh: exit status 1
Error: Invalid expression
on terraform_plugin_test.tf line 95, in resource "google_compute_service_attachment" "psc_attachment":
95: target_service = %{target_key == "l4ilb" ? "google_compute_forwarding_rule.producer_l4_ilb_fr.id" : "google_compute_forwarding_rule.producer_l7_ilb_forwarding_rule.id"}
Expected the start of an expression, but found an invalid expression token.
testing_new.go:79: Error retrieving state, there may be dangling resources: exit status 1
Error: Invalid expression
on terraform_plugin_test.tf line 95, in resource "google_compute_service_attachment" "psc_attachment":
95: target_service = %{target_key == "l4ilb" ? "google_compute_forwarding_rule.producer_l4_ilb_fr.id" : "google_compute_forwarding_rule.producer_l7_ilb_forwarding_rule.id"}
Expected the start of an expression, but found an invalid expression token.
Have you ran the tests locally? It helps make the review faster if you can verify that instead of waiting for CI debug results
|
Latest test run are now passing |
|
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: 1330 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
|
NickElliot
left a comment
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.
LGTM! thank you for the quick iteration
598e4df
Make Service Attachment's target_service field as Mutable. This allows for update of google_compute_service_attachment resource with target_service to happen In-place and not a recreate (destroy & create).
Fixes hashicorp/terraform-provider-google#25899
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.