-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add GA support for confidentialInstanceType #10887
Conversation
/cc @NickElliot |
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @c2thorn, 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.
Errors
|
This PR has been waiting for review for 2 weekdays. Please take a look! Use the label |
Changed to draft since the GA json change hasn't propagated to the Golang derived API package yet. |
please ping me when this is ready for review |
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.
Errors
|
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.
|
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: 6871 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
|
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: 6871 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
|
|
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.
|
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: 6870 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
@c2thorn the TestReadPlannedAssetsCoverage failure appears to be unrelated. The rest is good to go I think. |
|
Tests analyticsTotal tests: 6870 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
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.
can you try rebasing/pulling this branch to after #11037. This should fix the unit test failure
@@ -28,18 +28,18 @@ require ( | |||
github.com/sirupsen/logrus v1.8.1 | |||
go4.org/netipx v0.0.0-20231129151722-fdeea329fbba | |||
golang.org/x/exp v0.0.0-20240409090435-93d18d7e34b8 | |||
golang.org/x/net v0.25.0 | |||
golang.org/x/oauth2 v0.20.0 | |||
google.golang.org/api v0.180.0 |
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.
is this upgrade needed to support the field in GA?
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.
It is. The ConfidentialInstanceType field was added to the GA API very recently.
@@ -1025,13 +1025,6 @@ be from 0 to 999,999,999 inclusive.`, | |||
Description: `The Confidential VM config being used by the instance. on_host_maintenance has to be set to TERMINATE or this will fail to create.`, | |||
Elem: &schema.Resource{ | |||
Schema: map[string]*schema.Schema{ | |||
<% if version == "ga" -%> | |||
"enable_confidential_compute": { |
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.
even if this field has been made obsolete, removing fields are a breaking change as users may be using it in TF schema. You can deprecate the field and follow up with removal by following https://googlecloudplatform.github.io/magic-modules/develop/breaking-changes/make-a-breaking-change/#add-deprecations-and-warnings-to-the-main-branch-of-magic-modules
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.
I'm not removing it. The else condition is just becoming active. Is the Required: True
what needs to remain until a major release can fully deprecate it? I've added a deprecation message in another commit at least.
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.
Ahh, I misread the block. Got it!
No, it is not a breaking change to remove a requirement (only the reverse)
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: 3815 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
|
|
This is a very version-specific change, so I'm going to run tests in our separate GA environment as well just to be sure. If everything's good I'll come back and merge |
Thanks @c2thorn! |
Tests look good, failures were not relevant. LGTM |
Finalizes hashicorp/terraform-provider-google#14768
Fixes b/345255719