-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(config): add subcommand to generate configuration schema #12224
Labels
domain: config
Anything related to configuring Vector
Comments
Now that we have at least three "generating" commands would it make sense to reorganize them under
|
Yeah, that's a good point.
I'll make a note to research where we're at as far as the generation
subcommands for native encoding schema stuff, and come up with a solution
to switch to a parameterized subcommand instead.
…On Fri, Apr 15, 2022, 8:26 AM Spencer Gilbert ***@***.***> wrote:
Now that we have at least three "generating" commands would it make sense
to reorganize them under vector generate?
- vector generate: produces a populated Vector configuration
- vector generate-config-schema: produces the entire schema of
Vector's configuration
- vector config: produces a single JSON object from the provided
configuration files
- I *thought* there were issues for command/s to generate the schemas
for Vector Native codecs (both protobuf and JSON schema)
—
Reply to this email directly, view it on GitHub
<#12224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABWLF7WOGH4JFBXLEKILLDVFFOBBANCNFSM5TO4WYDA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We're going to defer the bit about Vector version, etc, being top-level metadata as it depends on more sophisticated logic for parsing the metadata helper attributes and passing things other than flags/string literals. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(This issue is a task related to #12141: Implement configuration schema RFC)
Once #12223 is complete, we'll need a way to start easily and consistently emitting the resulting configuration schema that we get for the primary Vector configuration. We'll provide this capability by adding a Vector subcommand --
vector generate-config-schema
-- that provides the simple glue logic for actually utilizingConfigurable
and outputting a valid JSONSchema document.List of outcomes/acceptance criteria:
vector generate-schema
will emit a valid JSONSchema documentThe text was updated successfully, but these errors were encountered: