HCL lock file "race" (composer apply step fails 'sporadicly' with multiple workers)

[borisvankatwijk]

We had the problem that a deploy with 4 workers could not initialize the hcl lock file consistently somehow.

Mach-compose apply step:

- name: MACH Composer apply working-directory: ${{ github.workspace }}/config env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} MCC_CLIENT_ID: ${{ secrets.MCC_CLIENT_ID }} MCC_CLIENT_SECRET: ${{ secrets.MCC_CLIENT_SECRET }} run: mach-composer apply --auto-approve -f tst-config.yaml --ignore-change-detection --workers=4 --force-init

https://github.com/katogroup/mach-commerce-platform/actions/runs/15156076650/job/42614211241

logs_38891949926.zip

Idea we mentioned while discussing;

• Take up lock file in github?

cc @demeyerthom