Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: concurrent deploy #4494

Open
vzhemchuzhnikov opened this issue Oct 7, 2024 · 0 comments
Open

feature: concurrent deploy #4494

vzhemchuzhnikov opened this issue Oct 7, 2024 · 0 comments
Assignees

Comments

@vzhemchuzhnikov
Copy link

Currently, if two users edit scripts, flows or apps at the same time, the last who is saving will overwrite any change made by the first user.
Multiplayer feature is somewhat helps, but:

  1. It only works with scripts
  2. It only available in EE

Even with the multiplayer feature enabled, it is possible to have a race condition.

At the bare minimum, whenever we are saving a file in Windmill, we could check if the currently deployed file hash is the one we started with. If it is not, we could reject a save and ask to manually merge changes to the latest version (e.g. with wmill cli).
But it would be even better if we could do this merging in the UI as well (this could also be an EE feature).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants