New Feature Request: Environment Lock File

[yaronuliel]

Current Status

When a new "blank" .lando.yml file is created (e.g. using lando init) - the file contains very little information about the versions it is about to install, and will install the latest version for each of the services in the recipe at the time of building the service containers.

Given that the file is also checked into the source control of the project - when another team member pulls the repo and starts the project - he/she might get different versions of the containers. Not only that, even when a version is defined - (e.g. when config -> php: 7.3) it might build different images on different times, depending on the installed lando version.

Suggested Solution

My suggestion is, that a new file, named .lando.lock will be generated when the environment is launched. The file should contain the specific versions and images that was installed, so that if the environment is launched again, when the file exists in the project - it will generate the same environment, rather than fetching the latest versions.

The idea is of course borrowed from files like package-lock.json and yarn.lock for package.json, and composer.lock for composer.json

Before diving deep into details about the file structure and the required data it should contain - I'd like to see if the community understand the need and find such feature useful, like I do.

[yaronuliel]

 Thoughts?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.