hugocasa 65b80ecbeb feat(forks): warn before enabling triggers/schedules that conflict with parent ...

set_trigger_mode and schedule's set_enabled now check whether the parent
workspace has the same path actively enabled. If so, the call is rejected
with a `fork-conflict:<kind>:<parent_id>` error unless the request includes
`force=true`. The frontend interprets the prefix to surface a confirm-to-
proceed dialog.

This is the placeholder safety net until the Phase 3 listener-suffix work
removes the conflict for the namespaceable kinds (Kafka/MQTT/NATS/Postgres/
Azure/GCP-CreateNew). For SQS, GCP-Existing, and schedules — where there's
no namespacing fix — the warning is the durable solution.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-29 18:42:29 +02:00

..

src

feat(forks): warn before enabling triggers/schedules that conflict with parent

2026-04-29 18:42:29 +02:00

Cargo.toml

refactor: extract 12 leaf crates from windmill-api (#7899)

2026-02-11 10:31:03 +00:00