Ensure that only one process can be applying a recipe at a time

Seems like a perfect use case for the lock service.

But can the drupal script access that? 🤔

If it fully bootstraps Drupal, which AFAIK it does, then it should be able to access all services.

I think we should address this in phase 2.

Added locking mechanism in recipe command execution, and tests.

Locks are very tricky when something is batched. Look at the ConfigImporter ... it uses the persistent lock service. We're going to need to do the same.

sriharsha.uppuluri → made their first commit to this issue’s fork.

Just updated the MR with latest code, the tests are failing.

Let's do this issue in core as it is a single well focussed issue. Can someone create a core MR and move the work there...

I'm new to the core contribution, setting the status to need review

Actually before reviewing could this be cleaned up some.

There are 2 forks with 4 branches and 2 MRs so not clear what's up for review.

As per @alex comment need to consider the core MR
"Let's do this issue in core as it is a single well focussed issue. Can someone create a core MR and move the work there..."

catch → changed the visibility of the branch 3401875-ensure-that-only to hidden.

catch → changed the visibility of the branch 11.x to hidden.

catch → changed the visibility of the branch 3401875-ensure-that-only-recipes-lock to hidden.

Moving the ticket status to Needs Review

See 3 tests being added but when I run the test-only feature only 1 is failing testLockPreventsConcurrentExecution. Would expect all the new tests to fail