Register a registry
Discovers a registry from its base URL: fetches its well-known document, negotiates the highest supported definitions/modules capability, and stores a record. The advertised id is used unless an explicit id override is supplied. The base URL is validated and normalized before storage. When auth credentials are supplied, the well-known auth advertisement is validated first: safety refusals (plaintext transport, method mismatch, a requested oauth2 scope the registry does not advertise) fail the request with 400, while a failed live token exchange still stores the record and reports error status on the auth field.
Body
Request body used to register a registry via discovery.
Absolute http(s) URL of the registry. A well-known discovery document is fetched from it; the URL is normalized before storage.
1Optional local id override. When omitted, the id advertised by the registry's well-known document is used.
1Optional credentials for the registry, validated against its well-known auth advertisement before storage.
- Option 1
- Option 2
Response
The registry record was created.
Response body of a registry registration request.
Registry slug matching /^[A-Za-z0-9_-]+$/ used as the primary key.
1Normalized absolute http(s) URL of the registry.
ISO-8601 timestamp of the last successful sync with the registry, or null when it has never been synced.
ISO-8601 timestamp of when the registry was registered.
ISO-8601 timestamp of the last mutation to the record.
Authentication method configured for this registry, or null when none is set.
apiKey, oauth2, null Epoch-ms timestamp when the cached OAuth2 access token expires, or null for api key auth or when no token has been fetched.
Outcome of storing the credentials supplied in the request, or null when no auth was supplied.