Use typed vendor lookups - #3082
Conversation
|
Skipping CI for Draft Pull Request. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe config store now resolves vendors by ChangesTyped vendor lookup propagation
Estimated code review effort: 3 (Moderate) | ~25 minutes Sequence Diagram(s)sequenceDiagram
participant GCredentials
participant GSecretDialogWrapper
participant GSecretDialogGeneric
participant GSecretDialog
participant ConfigStore
GCredentials->>GSecretDialogWrapper: pass visibleCredentialVendorType
GSecretDialogWrapper->>GSecretDialogGeneric: pass vendorType
GSecretDialogGeneric->>GSecretDialog: bind vendorType
GSecretDialog->>ConfigStore: vendorDisplayName({ type, name })
ConfigStore-->>GSecretDialog: return display name
Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
|
/kind enhancement |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@frontend/src/components/Credentials/GSecretDialogGeneric.vue`:
- Around line 81-84: Declare the required vendorType prop in
GSecretDialogAws.vue, GSecretDialogAzure.vue, GSecretDialogAlicloud.vue, and
GSecretDialogCloudflare.vue, then forward each wrapper’s vendorType value to the
imported GSecretDialog component. Preserve the existing wrapper behavior and use
the appropriate vendor identifier for each provider.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a51c97a6-30b7-4fab-8e35-6a44a75e17d7
📒 Files selected for processing (21)
frontend/__tests__/stores/config.spec.jsfrontend/src/components/Credentials/GBindingRowInfra.vuefrontend/src/components/Credentials/GCredentialRowDns.vuefrontend/src/components/Credentials/GSecretDialog.vuefrontend/src/components/Credentials/GSecretDialogGeneric.vuefrontend/src/components/Credentials/GSecretDialogWrapper.vuefrontend/src/components/Credentials/GSelectCredential.vuefrontend/src/components/GSeedListRow.vuefrontend/src/components/GShootListRow.vuefrontend/src/components/GVendor.vuefrontend/src/components/GVendorIcon.vuefrontend/src/components/NewShoot/GNewShootInfrastructureCard.vuefrontend/src/components/SeedDetails/GSeedInfrastructureCard.vuefrontend/src/components/ShootDetails/GShootInfrastructureCard.vuefrontend/src/components/ShootDns/GDnsProvider.vuefrontend/src/components/ShootDns/GDnsProviderRow.vuefrontend/src/components/ShootDns/GManageDns.vuefrontend/src/composables/useCloudProfile/useMachineImages.jsfrontend/src/store/cloudProfile/index.jsfrontend/src/store/config.jsfrontend/src/views/GCredentials.vue
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petersutter The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. DetailsGit tree hash: 04538fa3c5724dd0958a504d2c08a2f7b4b6fb10 |
What this PR does / why we need it:
This is the second preparatory refactor extracted from #2824 and follows the vendor registry extraction in #3075.
Vendor lookup previously accepted only a vendor name and searched across infrastructure, DNS, and machine-image vendors. This became ambiguous when multiple vendor domains used the same name and made it impossible for callers to state which registry they intended to query.
This change:
infra,dns, ormachineImage) and nameRelated PRs:
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
Please review this as the second preparatory refactor in the sequential split of #2824. The API change is intentionally mechanical: every lookup site now supplies its known vendor domain.
Validation:
make verifyRelease note:
Summary by CodeRabbit
Summary by CodeRabbit
Bug Fixes
Tests