Skip to content

VED-1238: Add moved blocks for TF state and plan #2321

VED-1238: Add moved blocks for TF state and plan

VED-1238: Add moved blocks for TF state and plan #2321

Triggered via pull request April 20, 2026 15:39
Status Failure
Total duration 11m 35s
Artifacts 23

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
22s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
28s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
9s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
3m 53s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
34s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
3m 54s
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 11 warnings
run-e2e-automation-tests (internal-dev-sandbox) / e2e-automation-tests
Failed to download archive 'https://api.github.com/repos/hashicorp/setup-terraform/tarball/5e8dbf3c6d9deaf4193ca7a8fb23f2ac83bb6c85' after 1 attempts.
run-e2e-automation-tests (internal-dev-sandbox) / e2e-automation-tests
An action could not be found at the URI 'https://api.github.com/repos/hashicorp/setup-terraform/tarball/5e8dbf3c6d9deaf4193ca7a8fb23f2ac83bb6c85' (B019:171155:8EFA:B384:69E64B2B)
run-e2e-automation-tests (internal-dev-sandbox) / publish-test-report
Unable to download artifact(s): Artifact not found for name: dev-pr-1430-internal-dev-sandbox-e2e-test-output Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
run-e2e-automation-tests (internal-dev) / wait-for-deployment
The strategy configuration was canceled because "run-e2e-automation-tests.internal-dev-sandbox" failed
run-e2e-automation-tests (internal-dev) / wait-for-deployment
The operation was canceled.
run-e2e-automation-tests (internal-dev) / publish-test-report
Unable to download artifact(s): Artifact not found for name: dev-pr-1430-internal-dev-e2e-test-output Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
PR Deploy and Test
The strategy configuration was canceled because "run-e2e-automation-tests.internal-dev-sandbox" failed
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 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 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 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 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 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 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 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/
deploy-pr-backend / Deploy ack-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 recordprocessor 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~04WOM3.dockerbuild
39.6 KB
sha256:2126f8377197d47778b74be1d502add2674faf086b6b5a1bc4af4485cd20275a
NHSDigital~immunisation-fhir-api~2XK100.dockerbuild
67.9 KB
sha256:b55d25c87017c6ccc4bd92698273ff1b668e67992ef5233e197438c52286f4bb
NHSDigital~immunisation-fhir-api~AJZRHV.dockerbuild
39.4 KB
sha256:31df44c2b08bdccf6371d9c2849f24f6afecc3feae3ef5750477549933fc4527
NHSDigital~immunisation-fhir-api~C43595.dockerbuild
39.6 KB
sha256:07752ae7220d508269da3bddecb31421fccfcfae4c7f796d402403379b07e515
NHSDigital~immunisation-fhir-api~LHJBR6.dockerbuild
39 KB
sha256:61571ac195025cafc5725425cad377f668ff371ee58b24198e8f142bae12139a
NHSDigital~immunisation-fhir-api~OAMKVS.dockerbuild
38.1 KB
sha256:18dbd5b2de396e6cdde27062dfb70b8f02329ddc43160542e5a4c134d196bcb6
NHSDigital~immunisation-fhir-api~Q9K6JJ.dockerbuild
39.2 KB
sha256:78371570fc5586e12edcf61d444efeb3316d554c295449fd72bb394082f2a621
NHSDigital~immunisation-fhir-api~SJDKQP.dockerbuild
39.4 KB
sha256:6c3060813def0b89e79bfb3a05824b2169a0fe3f58c6b7a73a612ef98e9c1d9e
NHSDigital~immunisation-fhir-api~T9QDKM.dockerbuild
39.4 KB
sha256:ac87f9eeada892568dca7911633cf753346fc1f49efacd52ddb92ed59f10def7
NHSDigital~immunisation-fhir-api~VMGUPF.dockerbuild
39.6 KB
sha256:a871bb974b6ab5771bcd1c81d215bcddf5ab57ac224096e94367e26a625a3097
NHSDigital~immunisation-fhir-api~X7ARPJ.dockerbuild
67.6 KB
sha256:808690d5c74a564b0aee131d912a1e4341d6272b3ffa437ef8994c72f445a098
deploy-manifest-ack-backend-dev-pr-1430-1
626 Bytes
sha256:afa3464a29abcb31d986ffe335017ae105675dc699722aab81b1f517a6d6a940
deploy-manifest-backend-dev-pr-1430-1
609 Bytes
sha256:99c81fc0fbf91841a6884c32065237a0a11cd1691d6d7cb3212ebc85ae136514
deploy-manifest-batch_processor_filter-dev-pr-1430-1
656 Bytes
sha256:12b49b4e48fbd7b028f653476d1e017760e0b04ff3312a01d3c1b44d3690047f
deploy-manifest-delta_backend-dev-pr-1430-1
629 Bytes
sha256:89b68626d21479b59cc4c773d8908bed5e126fc571881b359cd16993b081b146
deploy-manifest-filenameprocessor-dev-pr-1430-1
638 Bytes
sha256:437c5db13618deedf62646635e8f45036f21ce24525aee148e40d12679ede39a
deploy-manifest-id_sync-dev-pr-1430-1
612 Bytes
sha256:683a7994a324175efece027a5b666dcb3de2a18acab15e2063a149d6c56a4078
deploy-manifest-mesh_processor-dev-pr-1430-1
632 Bytes
sha256:715e509a048f8854203cbdb7d0c82b8fff1b4cda2ae7d4d6e814c544c95ff7f0
deploy-manifest-mns_publisher-dev-pr-1430-1
629 Bytes
sha256:a6f06ad1ea4d8792c63742a24fc8085104368d7d11448f273132c11ed27d3eda
deploy-manifest-recordforwarder-dev-pr-1430-1
632 Bytes
sha256:1a27d186e56ce983f0c9d2065ee7779de56fb17c2148387eb458233cd82d63b3
deploy-manifest-recordprocessor-dev-pr-1430-1
631 Bytes
sha256:07610e1bc1d5d71dae77ac272758c06020a8ee47b5ad903ac7802fe102fb3bca
deploy-manifest-redis_sync-dev-pr-1430-1
620 Bytes
sha256:1c18020085493d3fc63575d682ff7a0d40c31f801c49273a8a2bc4a3007a69dd
dev-pr-1430-tfplan
98.7 KB
sha256:93e7e5a59cfa9638a2258988b998c7324557a6595f180b56f4f6216479f1d751