feat(admin): add GET /admin/v1/services/:id/schema endpoint - #492
Open
fan-tastic-z wants to merge 1 commit into
Open
feat(admin): add GET /admin/v1/services/:id/schema endpoint#492fan-tastic-z wants to merge 1 commit into
fan-tastic-z wants to merge 1 commit into
Conversation
Expose a service's config and secret JSON Schema documents so management
clients (fde-admin, the CLI, future UIs) can render typed config forms
instead of asking users to hand-write JSON and rely on validation errors.
- GET /admin/v1/services/:id/schema returns {service_id, config, secret};
a null field means the service declared no such schema
- only the schema document content is returned, never the daemon-side path
- schema content is validated as JSON before returning
- consistent with existing "describe-the-structure" endpoints: catalog
exposes method input/output types, and the service object already exposes
ConfigSchemaPath
OctoBus still only validates config/secret against these schemas; exposing
them does not change the pass-through semantics. The secret schema carries
structure (type/required/enum) only, never instance secret values.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Expose a service's config and secret JSON Schema documents so management clients (fde-admin, the CLI, future UIs) can render typed config forms instead of asking users to hand-write JSON and rely on validation errors.
OctoBus still only validates config/secret against these schemas; exposing them does not change the pass-through semantics. The secret schema carries structure (type/required/enum) only, never instance secret values.