[GH-ISSUE #403] Draft State for Architecture Configurations #260

Closed
opened 2026-03-03 11:14:22 +03:00 by kerem · 0 comments
Owner

Originally created by @charanm927 on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/403

Originally assigned to: @jagadeesh507 on GitHub.

Description:

Introduce a draft state for architecture configurations in dFlow so users can work on server/service architecture changes without immediately applying them to the live environment. This allows teams to prepare and review setups before finalizing.

Acceptance Criteria:

  • Add “Draft” status to architecture definitions.
  • Allow users to save changes in draft without affecting the live configuration.
  • Provide a clear UI indicator when an architecture is in draft mode.
  • Enable publishing of a draft to make it active.
  • Store and track multiple draft versions if needed.

Benefits:

  • Reduces risk from incomplete or incorrect configuration changes.
  • Enables collaborative review before deployment.
  • Improves workflow for complex architecture planning.
Originally created by @charanm927 on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/403 Originally assigned to: @jagadeesh507 on GitHub. **Description:** Introduce a draft state for architecture configurations in dFlow so users can work on server/service architecture changes without immediately applying them to the live environment. This allows teams to prepare and review setups before finalizing. **Acceptance Criteria:** - Add “Draft” status to architecture definitions. - Allow users to save changes in draft without affecting the live configuration. - Provide a clear UI indicator when an architecture is in draft mode. - Enable publishing of a draft to make it active. - Store and track multiple draft versions if needed. **Benefits:** - Reduces risk from incomplete or incorrect configuration changes. - Enables collaborative review before deployment. - Improves workflow for complex architecture planning.
kerem closed this issue 2026-03-03 11:14:22 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dflow#260
No description provided.