Locking a Drupal environment (content and/or config)

I would like Lagoon to support the idea of locking environments which is independent of production/development flags.

As a client, I want to make WIP changes in an environments, and be certain that they are protected.

The problem is that Lagoon doesn’t have a standardised official notion of a “locked” environment. So if you look at GovCMS, there should be a way of saying “We’re about to sync the database” or “we’re about to import config” but you should be able to check a value from .lagoon.yml (or whatever) to be sure this is allowed.

My proposal is that there is a documented LAGOON_* environment variables for this purpose.

I sketched out how this might look (with GOVCMS name-spacing) here: https://github.com/govCMS/scaffold-tooling/blob/develop/scripts/govcms-deploy#L8-L12

(OUT OF SCOPE Moving content between environments is not Lagoon’s problem - this is solved in various ways, eg with deploy or entity_pilot modules.)

[tobybellwood]

is this another use case for being able to add and expose tags to Lagoon envs… https://github.com/amazeeio/lagoon/issues/1289

[bomoko]

Hi all, So we’re going through our (not insubstantial) feature request list at the moment, categorizing and closing what doesn’t make sense anymore.

I think that this may have made a lot more sense when Lagoon was more tightly integrated with Drupal, but it feels like with metadata and environment variables this is something that can be enforced by users at a project level.

I’m going to close this for now - but I will raise this in the Dev Experience team - we might want to resurrect this idea as something like a “lagoon recipe” and write up how one might achieve this using Lagoon.