Manage deployment from the provisioner (openfn deploy) if an editor is active (editing) on a workflow in a project
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We currently prevent simultaneous editors in a workflow to preserve data integrity by ensuring that users don't overwrite other collaborators' work because they are actively working on a workflow. This works today but we don't stop users from running cli deploy which can also overwrite changes to a workflow if the deploy operation is executed.
We need to be able to check if any workflow is actively been edited and exclude it from being overwritten. Other workflows in the project can be updated except the one with an active user who is not a viewer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the openfn deploy command and trace how it selects and updates workflows, then inspect the existing active-editor protection. Done means deployment updates workflows without an active non-viewer editor while still updating other workflows in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100