-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Generate Structs for Flags or Output machine-reable description for flags #3924
Comments
Self-describing-binaries is kind of how I see this. I like this idea a lot. I personally think just a json blob that describes the subcommands and flags of those is a really fantastic start. Little can do a lot here I believe. |
@brancz Great idea! Having a subcommand to output this would be an amazing convenience. I wonder if something similar already exists? |
Something like /~https://github.com/alecthomas/kong might help you. |
There is also /~https://github.com/bwplotka/flagarize |
@bwplotka's gonna kill me how I've forgotten about |
Nah, fllagarize is dead 🙃 I would vote for /~https://github.com/openproto/protoconfig as this was created exactly for this purpose. |
I just had chat with @smintz, co-creator of similar project /~https://github.com/protoconf/protoconf, I think we plan to join forces into going for proto based configuration (alongside flags ofc) |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
To be able to conveniently generate type-safe configurations for Thanos. This could be utilized by the configuration projects (e.g
kube-thanos
or similar projects). We would like to have structs that define flags and configuration for Thanos.Flags could be generated from those structs or structs can be generated from existing flags.
Any change should be seamless to users, we shouldn't change any behaviour.
Any ideas? WDYT?
@thanos-io/thanos-maintainers
related: thanos-io/kube-thanos#184
The text was updated successfully, but these errors were encountered: