feat(frontend) Move shoot-specific defaults from branching logic to vendor configurations - #3167
feat(frontend) Move shoot-specific defaults from branching logic to vendor configurations#3167grolu wants to merge 3 commits into
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What this PR does / why we need it:
Moves shoot-specific defaults from branching logic in
utils/shoot.jsinto the infrastructure vendor configurations.This includes:
useShootContextnow resolves these settings through the configured infrastructure vendor. The AWS IOPS behavior introduced by #2951 is preserved:cloudProfile.spec.typegp2io1andio2The PR also adds default shoot manifest coverage for all configured infrastructure providers and focused regression coverage for the AWS volume behavior.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
This is intended to be a behavior-preserving refactoring that makes shoot defaults extensible through vendor configuration.
This is the last slice of #2824
Release note: