-
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
Enable EXTERNAL_MANAGED resource examples for GA #5660
Enable EXTERNAL_MANAGED resource examples for GA #5660
Conversation
Hello! I am a robot who works on Magic Modules PRs. I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. Thanks for your contribution! A human will be with you soon. @melinath, please review this PR or find an appropriate assignee. |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 4 files changed, 112 insertions(+), 6 deletions(-)) |
/gcbrun |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 4 files changed, 112 insertions(+), 6 deletions(-)) |
/gcbrun |
Hi @AlexanderEllis! Looks like the feature is already implemented in GA, but only the tests/examples are in beta, right? Sorry that I did not notice we were only testing in beta in the previous PR! |
Yup that's right! The feature has actually only been enabled in the GA API since my last PR, so it made sense to only test via the beta API at the time. They're now moving towards GA (starting with availability in the API), which is why I'm following up with this 👍 |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 4 files changed, 112 insertions(+), 6 deletions(-)) |
Okay! I just kick off the tests. Looks like the last one got timed out! Sorry about it. |
Yeah! I remember about it! I tested it locally with the compute backend service in the GA provider in the first PR and it failed. It makes sense now. Thanks @AlexanderEllis! |
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.
Looks like we have beta only
in the description of load_balancing_scheme
in google_compute_global_forwarding_rule
(https://github.com/GoogleCloudPlatform/magic-modules/blob/master/mmv1/products/compute/api.yaml#L4267)
Should we also modify this?
I am trying to understand here. So the field was not just beta only but EXTERNAL_MANAGED
was, and now we want to GA this option, right?
Yup that's right, only EXTERNAL_MANAGED was beta, and now we want to GA it (which is really GA'ing the examples and tests I believe). And as far as that "Beta only", that's a good question. AFAICT it looks like that might have been added just in reference to the following PRIVATE_SERVICE_CONNECT configuration? 5f8d650 in #4358: |
I think you are absolutely right! Then everything looks good to me! Thanks @AlexanderEllis |
One last change for the Global External HTTP(S) Load Balancer to remove the beta-only requirement for the examples and tests. This is for the
EXTERNAL_MANAGED
load_balancing_scheme
option forgoogle_compute_global_forwarding_rule
andgoogle_compute_backend_service
.Really fixes hashicorp/terraform-provider-google#10858
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)