Skip to content

Is there a standarized way to validate configuration? #219

Description

@alexppg

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.

Activity

  1. alexppg commented on Feb 12, 2021

    @alexppg
    MemberAuthor

    @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.

  2. alexppg commented on Feb 13, 2021

    @alexppg
    MemberAuthor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions