Update disk type schema field to support db-c4a-highmem-4 tier#13236
Update disk type schema field to support db-c4a-highmem-4 tier#13236NickElliot merged 11 commits intoGoogleCloudPlatform:mainfrom
Conversation
…type internally when not specified
…y decide disk type when not specified
|
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @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. |
|
@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
@GoogleCloudPlatform/terraform-team @NickElliot This PR has been waiting for review for 1 week. Please take a look! Use the label |
NickElliot
left a comment
There was a problem hiding this comment.
clarifying the description, let me know if this wording isnt accurate!
|
@shuang2018g, this PR is waiting for action from you. If no action is taken, this PR will be closed in 28 days. Please address any comments or change requests, or re-request review from a core reviewer if no action is required. This notification can be disabled with the |
|
@NickElliot can we make the following edit on L1675 in I created a PR to update this value but Shuang is OOTO. Reason for this request is that the public tier name for C4A was changed, you can refer the new name in the documentation here. |
|
@shuang2018g, this PR is waiting for action from you. If no action is taken, this PR will be closed in 14 days. Please address any comments or change requests, or re-request review from a core reviewer if no action is required. This notification can be disabled with the |
|
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.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. |
Tests analyticsTotal tests: 109 Click here to see the affected service packages
Action takenFound 83 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! |
NickElliot
left a comment
There was a problem hiding this comment.
A question about default behaviors on the resource:
while this wouldnt be a breaking change, is there scenarios where a resource made today with Terraform (that would've ended up with the present PD_SSD default) will end up with a different default disk_type upon creation of an identical configuration?
The existing configuration should continue to get PD_SSD as the default storage. |
No, Hyperdisk will only be set as the default disk type for newly launched C4A (still in preview) machine series in CloudSQL. So customer would have to explicitly configure the resource to use C4A series public tier for the disk type to default to Hyperdisk. |
|
@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
NickElliot
left a comment
There was a problem hiding this comment.
please resolve the conflicts!
8b492b7 to
e6387cb
Compare
|
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.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. |
Tests analyticsTotal tests: 111 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.
LGTM, change is non breaking due to the default being replaced with computed. All current configs will produce the PD_SSD output by default still, change allows for compatibility with new machine types.
f0f9f81

New CloudSQL performance tier does not support PD_SSD, specifying PD_SSD as default disk type can cause creation failure unnecessarily. Update the field to computed without default allows CloudSQL to automatically choose the right disk type when not specified.