## Summary If you exit out of the dev container before fully building an environment the gitlab provisioning data created as part of `provision-cluster` is deleted. The `assemble-inventory` script will still pass but will print out the error `jq: error: Could not open file /repo/gitlab_provisioning_data.json: No such file or directory`, running `run-orchestration` after this will result in a failed build. ```ansible TASK [Create common partial configuration] *********************************************************************************************************************************************************************************************** fatal: [nw-orchestrator-gitlab-consul-1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: No first item, sequence was empty."} fatal: [nw-orchestrator-gitlab-consul-2]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: No first item, sequence was empty."} fatal: [nw-orchestrator-gitlab-consul-3]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: No first item, sequence was empty."} ``` ## Environment <!-- Fill in the values --> |-|-| | Orchestrator Version | [01d1cba7](https://gitlab.com/gitlab-org/gitlab-orchestrator/-/commit/01d1cba7c773dee47d371a8f2f0f1bee9f0ac0d7) | | Deployment Environment | GCP | ## Expectation The dev container should persist any files required to allow a build to be carried out over multiple sessions ## Actual Result Currently if you do not complete the full build process before exiting the dev container then you will need to rerun every prior command before running `run-orchestration` ## Steps to Reproduce <!-- How can the bug be reproduced using ordered steps? --> 1. `./scripts/dev-container/build-dev-container` 1. `./scripts/dev-container/run-dev-container` 1. `./provision-cluster` 1. `./assemble-inventory` 1. exit the dev container 1. `./scripts/dev-container/run-dev-container` 1. `./run-orchestration` ## Contextual Information <!-- Add any necessary contextual flavor that may be relevant --> Neither of the files created by both `provision-cluster` and `assemble-inventory` will persist after exiting the dev container, this means that they will always need to be run before running `run-orchestration` when reentering a dev container. <!-- Labels here -->