Skip to content

feature: introduce a more robust validation mode #190

Closed
@hbagdi

Description

@hbagdi

Currently, decK provides a validate command which does JSON schema validation of the input and also creates an in-memory state. While this detects some errors with user-input, we can do more.
Kong ships with a validate endpoint for each entity:
https://docs.konghq.com/2.0.x/db-less-admin-api/#validate-a-configuration-against-a-schema

A new mode for validate command (gated using a boolean CLI flag) should run all the entities present in the state against the Admin API endpoint. This should catch almost all errors with the user input.

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