Skip to content

Deploy Backend - dev ref #126

Deploy Backend - dev ref

Deploy Backend - dev ref #126

Manually triggered April 22, 2026 11:28
Status Success
Total duration 6m 32s
Artifacts 25

deploy-backend.yml

on: workflow_dispatch
Matrix: deploy-lambda-images
terraform-plan
46s
terraform-plan
terraform-apply
3m 57s
terraform-apply
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
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 mock_pds 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 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 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 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 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 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 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 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 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 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/
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/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~0NJXZV.dockerbuild
66.6 KB
sha256:36ef26bad61c6ebcbe0c67c1362d3192ad7729caa180edd5047e39610dcad144
NHSDigital~immunisation-fhir-api~3HJGMD.dockerbuild
66.2 KB
sha256:f8748e56eb8a6694c408928f41a92d04ed9fcf216df0cd9edb8acc42b66479bd
NHSDigital~immunisation-fhir-api~59ZS1S.dockerbuild
67.3 KB
sha256:fa938020ca74d54f353983123b83f391fbc89d78c2b7312dd6f722039b3c346d
NHSDigital~immunisation-fhir-api~ERP1OB.dockerbuild
67.8 KB
sha256:f17bdf9761d0b7de08003850a9b51d339a1586c063b83d6f6a1fcb1d6c03cf31
NHSDigital~immunisation-fhir-api~FE4WMZ.dockerbuild
67.6 KB
sha256:25d5381d15f983c0f2e036fcab53c57c4c0742a6413d5470baf4dc8b8c417616
NHSDigital~immunisation-fhir-api~LU8PFB.dockerbuild
64.5 KB
sha256:e9d8c0be03be4caa49feec64ff3bd6adb6cda44590e6e6489af0fcea985cd167
NHSDigital~immunisation-fhir-api~NNG3N0.dockerbuild
66.6 KB
sha256:f7b6dc08e2ae3620a5b4f66f72560fb2733e8a826a521d8031ca239780a11bf9
NHSDigital~immunisation-fhir-api~OI8846.dockerbuild
67.7 KB
sha256:60aeba1619fb21708618d2f0fc192640bd79207a409387383de2bdee7447e960
NHSDigital~immunisation-fhir-api~P2BP5E.dockerbuild
66.4 KB
sha256:064ca36fbcbe1c655349259975790269a2cb43beb3c105ab0e3455a725c5e393
NHSDigital~immunisation-fhir-api~T7R656.dockerbuild
42.7 KB
sha256:fd021e98c6241d0b82148514269641984a191b4cc4d9e628a8da33ae8eff6a73
NHSDigital~immunisation-fhir-api~XX56MB.dockerbuild
67.8 KB
sha256:f7bb167c62feecbdbb534c75cdd1594559c9ae7e1b2a804eb21a0530424df846
NHSDigital~immunisation-fhir-api~ZH5G24.dockerbuild
65.8 KB
sha256:15d8713cac0c031ab82fff3df535094f3e2f12ba05ead47d08a40403583c81dc
deploy-manifest-ack-backend-dev-ref-1
637 Bytes
sha256:4a5c2f1afdc6fa3b9cbc8b5f852961102a25fa70f5ff4feb4cb1c776109a806c
deploy-manifest-backend-dev-ref-1
620 Bytes
sha256:d047e3e59a8b7d2f62fa2733a055c4d62e701eee265f954de1d6c5490b3da323
deploy-manifest-batch_processor_filter-dev-ref-1
670 Bytes
sha256:1bca29812f06e48eac9edc39e332948e31115ba51c41a570a24851d7e689dce6
deploy-manifest-delta_backend-dev-ref-1
640 Bytes
sha256:df9795702d733616f40bd036dd657c5e0b81e6a62b7fb8910804dd6aac5e46ef
deploy-manifest-filenameprocessor-dev-ref-1
652 Bytes
sha256:24230d6c23bd6b4320227b067c9ec092e70fef25056da160bcf3159171960ea9
deploy-manifest-id_sync-dev-ref-1
625 Bytes
sha256:5bb3ef5727e0baa6b2d4dc236b6473ad2296f01ae3e0d44d91567eb2c32814a0
deploy-manifest-mesh_processor-dev-ref-1
646 Bytes
sha256:d7b26f2064b656310a513c7b90d390264bee37d71018f345aa5308162abd0103
deploy-manifest-mns_publisher-dev-ref-1
644 Bytes
sha256:371d75a83354c3690f62ff40396fe2d240b06b69676c7e8e880cf1094db07c0d
deploy-manifest-mock_pds-dev-ref-1
627 Bytes
sha256:e0619e1872706669d6632de48cc79e63125ee432c3b3860a22bf0cc0818ddc79
deploy-manifest-recordforwarder-dev-ref-1
647 Bytes
sha256:9fc1eac2c4901e0e5e1db76f8db87e91e9c5d687dd37e1fe939185485791586a
deploy-manifest-recordprocessor-dev-ref-1
645 Bytes
sha256:01a47efa1308caacd60bdb42b95db2b78f587d902f56a9a35a619a41b8aa93c9
deploy-manifest-redis_sync-dev-ref-1
636 Bytes
sha256:22d1e025c95e1829d53042cc739cff7b69d368baab8c8fd08984d42899d62663
dev-ref-tfplan
224 KB
sha256:6685ec2d2d59069c167935863ec86d70af1fbef976d2f658ff8810f34c648b2d