Introduce functionality (dis)allowing to use the UI Editor to edit flows

kestra-io / kestra

Infinitely scalable, event-driven, language-agnostic orchestration and scheduling platform to manage millions of workflows declaratively in code.

https://kestra.io

Apache License 2.0

7.11k stars 422 forks source link

Introduce functionality (dis)allowing to use the UI Editor to edit flows #3496

Open anna-geller opened 3 months ago

anna-geller commented 3 months ago

Feature description

Some users expect flows to be not editable from the UI i.e. only allowing changes to be pushed to production namespace/tenant/instance via CI/CD, Git Sync system flow etc.

To match the syntax of many other properties (e.g. namespaceFiles), we may add the enabled flag as follows:

id: myflow
namespace: prod
editor:
  enabled: false
tasks:
...

loicmathieu commented 3 months ago

I would vote for readOnly: true as we usually create complex properties only when we need more than one sub properties and read only is a pretty usual concept.

anna-geller commented 2 months ago

internal info why we made a decision for that implementation https://www.notion.so/kestra-io/Why-editor-enabled-rather-than-readOnly-10c14d07d84540cda28217a94148410d?pvs=4