Is your feature request related to a problem? Please describe.
If KTB manages the cluster in a multi-tenant environment there is currently no way to assure only one is running. If two people change the same environment in two different pipelines we should enable the possibility to use locks, basically serializing the execution.
Describe the solution you'd like
When run using a remote cluster manager, this should be Redis but as well the upcoming S3 or others, allow the possibility to have a .lock file. Execution will wait until .lock file is removed before continuing.
Is your feature request related to a problem? Please describe.
If KTB manages the cluster in a multi-tenant environment there is currently no way to assure only one is running. If two people change the same environment in two different pipelines we should enable the possibility to use locks, basically serializing the execution.
Describe the solution you'd like
When run using a remote cluster manager, this should be Redis but as well the upcoming S3 or others, allow the possibility to have a .lock file. Execution will wait until .lock file is removed before continuing.