:zap: Workflow Automation Platform. Orchestrate & Schedule code in any language, run anywhere, 500+ plugins. Alternative to Zapier, Rundeck, Camunda, Airflow...
See here where I had to introduce some temporary config to be able to serve inputs & outputs prior to the bug introduction.
We must find a way to handle it while not introducing a breaking change.
From my observations, there is a lot of issues around paths where most of webserver endpoints are sending the Kestra schema to storage while storage already adds it leading to a lot of duplicate slash.
Moreover the root cause is that the introduction of tenants added a leading slash to every paths that lead to unability to read execution inputs & outputs prior to Kestra v0.15.
Describe the issue
See here where I had to introduce some temporary config to be able to serve inputs & outputs prior to the bug introduction.
We must find a way to handle it while not introducing a breaking change. From my observations, there is a lot of issues around paths where most of webserver endpoints are sending the Kestra schema to storage while storage already adds it leading to a lot of duplicate slash.
Moreover the root cause is that the introduction of tenants added a leading slash to every paths that lead to unability to read execution inputs & outputs prior to Kestra v0.15.
Environment