Skip to content

VED-1238: Refactor all remaining lambdas deployment to a dedicated pipeline stage #2319

VED-1238: Refactor all remaining lambdas deployment to a dedicated pipeline stage

VED-1238: Refactor all remaining lambdas deployment to a dedicated pipeline stage #2319

Re-run triggered April 20, 2026 14:42
Status Failure
Total duration 2m 0s
Artifacts 20

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
21s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
33s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
6s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
4m 3s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
9s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 9 warnings
deploy-pr-backend / terraform-plan
Process completed with exit code 2.
deploy-pr-backend / terraform-plan
Terraform exited with code 1.
deploy-pr-backend / Deploy delta_backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy redis_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy filenameprocessor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy batch_processor_filter image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy mesh_processor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy mns_publisher image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy recordforwarder image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy-pr-backend / Deploy id_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~CX7GCO.dockerbuild
71.5 KB
sha256:d5e2ca7db3622ca5711f4216bf68ceeecddc61b4e7beb33ca633bb9e5451b8d0
NHSDigital~immunisation-fhir-api~G9V31C.dockerbuild
71.9 KB
sha256:6f531cd6090e3c3e7ab300b9cdb4762aa5a81f9d85ef647c62a6df58b161c5bf
NHSDigital~immunisation-fhir-api~L9ED1N.dockerbuild
72.7 KB
sha256:9b76b26816433a59f77783e25b3b3a4c23da346a91d8c0dc0ef86154c829d403
NHSDigital~immunisation-fhir-api~ND0HOX.dockerbuild
71.1 KB
sha256:586ed8d5104eb55385c20bf02d58bee7e81605289956e6fd26e9ddde3761fe1e
NHSDigital~immunisation-fhir-api~RK5P85.dockerbuild
73.4 KB
sha256:63744f8de042cfd4ed7c4ef5d5a18aeaab1823319dfa6b74d8aa50099dbd21e8
NHSDigital~immunisation-fhir-api~RRV3ER.dockerbuild
74.8 KB
sha256:3fcbdc81b8584c5aad8dc1eeaa091dad264b1634b8fc11a1e7e2c5d7d29f246b
NHSDigital~immunisation-fhir-api~ST875B.dockerbuild
72.4 KB
sha256:d6e671cc7b86120da5c4506f82384b92029fe38d7d21d85a13ec9d3d93c4cd94
NHSDigital~immunisation-fhir-api~TF75U9.dockerbuild
72.6 KB
sha256:e7069741b9b6ca27f1b1945058ad2800b367b4436d2b2dd5e9a1f53ee7087897
NHSDigital~immunisation-fhir-api~WPT3SP.dockerbuild
73.3 KB
sha256:d0cd9a5ce278f49ae9ccb7e245dea32cd4704ea47824f9abf190a3e518543886
deploy-manifest-backend-dev-pr-1414-2
609 Bytes
sha256:0f16bcbc82395e9e01f31d753a4e607af3a29ad64031baa14180153f5144ac18
deploy-manifest-batch_processor_filter-dev-pr-1414-2
656 Bytes
sha256:e3baefa8696917f2131babcdfaa6b578d4e38288907f36d2f3006f5395c1a8b9
deploy-manifest-delta_backend-dev-pr-1414-2
628 Bytes
sha256:91c1e9b509d5eb96d2c065dab12e088ee685fa0cdcf21b8bc88200c2ab8d3ead
deploy-manifest-filenameprocessor-dev-pr-1414-2
639 Bytes
sha256:854eea993e14c50b7dbd9ef2d1323c4da3b2cd49081a25217f279063c0486e4a
deploy-manifest-id_sync-dev-pr-1414-2
613 Bytes
sha256:39221ff3550166fd4ebe216f33d3bcfbb0eb54ff16d880ae840f6585a7c38e16
deploy-manifest-mesh_processor-dev-pr-1414-2
633 Bytes
sha256:aba456a57ffee7354c8b52a1847c658f724c6e741314e426c2db8bb3ae124a46
deploy-manifest-mns_publisher-dev-pr-1414-2
630 Bytes
sha256:a7e30c9a4dad0f2c6a4a0ce908951ad475ca604d28a7cb92a36438142c784678
deploy-manifest-recordforwarder-dev-pr-1414-2
632 Bytes
sha256:bd3b0c5725e6a6413f5eca7e663d61069453649b4e15ee5c3f84529fb8cc553e
deploy-manifest-redis_sync-dev-pr-1414-2
622 Bytes
sha256:28091a418c45706d6832c4e1819f5758ba90f513d6b98feaae7f38bb48fd598e