:zap: Workflow Automation Platform. Orchestrate & Schedule code in any language, run anywhere, 500+ plugins. Alternative to Zapier, Rundeck, Camunda, Airflow...
I'm working on updating the json schema for Kestra flows over at https://json.schemastore.org/. I've followed the same process I usually do but this time the checks fail, it seems to relate to the below section of code.
Looking at format it would seem to be related to matching a pebble string? The json schema spec seems to imply that pattern could be used. I updated the schema with "pattern": ".*\\{\\{.*\\}\\}.*" and this then passes the checks in the json schema git repo. What I'm not sure is how it's used with Kestra and would making this change lead to any issues?
Describe the issue
I'm working on updating the json schema for Kestra flows over at https://json.schemastore.org/. I've followed the same process I usually do but this time the checks fail, it seems to relate to the below section of code.
Looking at
formatit would seem to be related to matching a pebble string? The json schema spec seems to imply thatpatterncould be used. I updated the schema with"pattern": ".*\\{\\{.*\\}\\}.*"and this then passes the checks in the json schema git repo. What I'm not sure is how it's used with Kestra and would making this change lead to any issues?https://github.com/kestra-io/kestra/blob/78f5ff2b7b085a9ad117e701ae0c59e1c9e7b27e/core/src/main/java/io/kestra/core/docs/JsonSchemaGenerator.java#L278
Environment