-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat(entities): config store secret #1601
Conversation
const deleteAssociatedConfigStore = async (configStoreId: string): Promise<void> => { | ||
const { apiBaseUrl, app, controlPlaneId } = (props.config as KonnectVaultListConfig) | ||
const url = `${apiBaseUrl}${endpoints.list[app].deleteConfigStore}` | ||
.replace(/{controlPlaneId}/gi, controlPlaneId || '') | ||
.replace(/{id}/gi, configStoreId) | ||
try { | ||
await axiosInstance.delete(url) | ||
} catch (error: any) { | ||
// There is a rare case where more than 1 vaults are linked to the config store (i.e. created via API). | ||
// In this case, the deletion will fail but the UI can safely ignore the error. | ||
} | ||
} |
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.
qq: Would we delete the associated config store if a user tries to delete a Konnect vault from the vault detail page as well?
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.
Yes I think we should. I'll add this logic in the host app.
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.
Functionally tested the vault and secret picker features and LGTM. Left a non-blocking question.
Summary
Integrate Konnect Vault with Konnect Config Store
KM-445
Resources