Repository navigation
Integrations: store access details for USI, VEVO, PRISMS and DataZoo - #36
Merged
Merged
Conversation
…ahead of their connectors Add Connection gets 'Store access details' on each pending app; its setup panel has API key / secret, account or client ID, organisation or provider code and environment. New Edge Function integrations-credentials (deployed v1, JWT on) writes them to Vault through integration_credential_write; values are never returned. Nothing is sent to a provider; no connector yet. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YMiuVrVzqwLZcPj4wybCKi
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lets an administrator store access details for USI, VEVO, PRISMS and DataZoo before their connectors exist, so they only have to paste them when the provider issues them.
integrations-credentials(deployed on hosted as v1, JWT on): same access checks as integrations-admin, writes one JSON document to Vault throughintegration_credential_write. Nothing is sent to a provider.Checks: type-check PASS, lint PASS, build PASS; function answers OPTIONS 200 and 401 without a token. NOT RUN: signed-in save.
Generated by Claude Code