Skip to content
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

Is there a standarized way to validate configuration? #219

Open
alexppg opened this issue Oct 31, 2020 · 2 comments
Open

Is there a standarized way to validate configuration? #219

alexppg opened this issue Oct 31, 2020 · 2 comments

Comments

@alexppg
Copy link
Member

alexppg commented Oct 31, 2020

Is your feature request related to a problem? Please describe.
It would be useful that before trying to start a MS, pyms checks that the configuration is using is valid. I understand that in here

def validate_conf(*args, **kwargs):
there's some kind of validation. But it seems on high level, it doesn't validate per service, for example.

Describe the solution you'd like
I'd like that every service states clearly its configuration schema and that this can be validated at when starting the microservice.

@alexppg
Copy link
Member Author

alexppg commented Feb 12, 2021

@avara1986 Hey, would it be interesting this feature using https://github.com/keleshev/schema? It seems pretty interesting. This way, the configuration that a service (or whatever) supports would be explicit, right now it's kind of implicit or to see it, you have to go to inspect the service's code.

@alexppg
Copy link
Member Author

alexppg commented Feb 13, 2021

Also, not sure if related to this, but I think there should be a general way to set some sane defaults for all modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant