-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Added update support to sslPolicy field in region_target_https_proxy #10877
Added update support to sslPolicy field in region_target_https_proxy #10877
Conversation
…xy and related test;
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. |
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: 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 testsTestAccComputeInstanceNetworkIntefaceWithSecurityPolicy|TestAccComputeRegionTargetHttpsProxy_addSslPolicy_withForwardingRule|TestAccComputeRegionTargetHttpsProxy_update |
|
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.
Just a small question in the test config. I believe the failing test is unrelated and is failing for all PRs, so it should be safe to ignore
url_map = google_compute_region_url_map.default-https.self_link | ||
ssl_certificates = [google_compute_region_ssl_certificate.foobar0.self_link] | ||
|
||
lifecycle { |
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.
Why do we need create_before_destroy here?
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.
After re-testing, those fields don't appear to be as necessary as I expected, I will be removing them.
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: 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 testsTestAccComputeInstanceNetworkIntefaceWithSecurityPolicy |
|
Adds support to update "ssl_policy" field in "compute_region_target_https_proxy" via the PATCH endpoint, removing its ForceNew flag, as well as related tests;
Fixes: hashicorp/terraform-provider-google#16963
Release Note Template for Downstream PRs (will be copied)