Repository navigation
feat(relay): look up a platform's --metadata keys instead of a hardcoded table (v2.17.0) - #245
Merged
Merged
Conversation
…ded table (v2.17.0)
`one relay metadata <platform>` reads the setup fields One already stores
per platform (GET /v1/webhooks/relay/config/{connectorId}, the list the
dashboard's Configuration step shows) and prints each key with its label,
whether it's required, and whether it's a secret. A secret field's
placeholder is never repeated.
`relay create --create-webhook` checks the required keys before calling
the API. When one is missing it returns `status: "metadata_required"`
with the missing fields, exits 1, and creates nothing. Before, the
endpoint was created, the webhook never registered, and only a warning
said why. When the field list can't be read, or One stores none for the
platform, create goes ahead as before.
The 49-row metadata table in the skill and `one guide relay` is gone;
both now point at the command. README and --help updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
paulkr
force-pushed
the
feat/relay-metadata-fields
branch
from
November 20, 2026 03:02
6b8d9fc to
831518b
Compare
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.
What this does
one relay metadata <platform>. It reads the setup fields One already stores per platform (GET /v1/webhooks/relay/config/{connectorId}, the list the dashboard's Configuration step shows). For each key it prints the label, whether it's required, and whether it's a secret. A secret field's placeholder is never repeated, because some stored placeholders look like real secrets.relay create --create-webhookchecks the required keys first. When one is missing it returns"status": "metadata_required"with the missing fields, exits 1, and creates nothing. Before, the endpoint was created, the webhook never registered, and only awarningsaid why. If the list can't be read, or One stores none for the platform, create goes ahead as before.skills/one/references/relay.mdandone guide relay. Both now point at the command. README and--helpupdated. Version 2.17.0.No backend change: the endpoint already exists and accepts API keys.
Merge after the integration team fixes four config rows
The stored rows are hand-maintained and some have drifted from the server code. Most gaps only mean the check has nothing to go on (it falls back to today's warning). Four rows, though, mark a key required that the code doesn't need, so once this ships the CLI would ask for it:
fillout:FILLOUT_SIGNING_SECRETis never readtypeform:TYPEFORM_TAGhas a defaultlinear:LINEAR_TEAM_IDis optional (requiring it narrows the webhook to one team)whop:WHOP_ACCOUNT_IDis optionalThe full list for the integration team covers all 105 platforms.
Checks
src/commands/relay-metadata.test.ts, against a fake API.resolveConfigtests, which fail the same way on a cleanmainon this machine.relay metadata github,mondayandstripereturn the stored fields, or an empty list for stripe.relay create --create-webhookwith a made-up GitHub connection key and onlyGITHUB_OWNERis refused (exit 1) before any request to create.Related
optionalin the webhook form; same prompt)🤖 Generated with Claude Code