Skip to content

Deploy Backend - dev pr-1427 #123

Deploy Backend - dev pr-1427

Deploy Backend - dev pr-1427 #123

Manually triggered April 21, 2026 16:13
Status Success
Total duration 3m 44s
Artifacts 25

deploy-backend.yml

on: workflow_dispatch
Matrix: deploy-lambda-images
terraform-plan
49s
terraform-plan
terraform-apply
1m 36s
terraform-apply
Fit to window
Zoom out
Zoom in

Annotations

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

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~5WOZ2R.dockerbuild
36.3 KB
sha256:5cd1d83093de9bb9f284785a018c0c5512ec3644623b5a65a26d22d9f3ab327d
NHSDigital~immunisation-fhir-api~A7F0FM.dockerbuild
44.1 KB
sha256:a1ad0136460be0760df2ddb12343338a54297e63863c33ee5e6fbab4f4a41809
NHSDigital~immunisation-fhir-api~H4RFZB.dockerbuild
39.3 KB
sha256:4503697dfa952dfbbf694115bbee033ec419646e321fc0b0d0353e082a2adbf7
NHSDigital~immunisation-fhir-api~JSNSZ3.dockerbuild
45.6 KB
sha256:ef7d358b1b85dbf6feaa16a3bd3dec035a25e38c486f86a005745d7a212bcad9
NHSDigital~immunisation-fhir-api~JZOT5S.dockerbuild
43.5 KB
sha256:e107f656dbd0640be9b828f01bfc37aeb6f849c6f2da52d95d691d4a850b15c6
NHSDigital~immunisation-fhir-api~LRYD3F.dockerbuild
38.5 KB
sha256:9bc092451a3510d6cf59e926190055c8ef649d91036048177436d57db0ff1e0f
NHSDigital~immunisation-fhir-api~OINZ4L.dockerbuild
45.4 KB
sha256:85b58f61f573cea101829fb0607d139c9d204ec8e80b0d926ef7226b3af6d9dc
NHSDigital~immunisation-fhir-api~UG8Y82.dockerbuild
63.3 KB
sha256:bbdfbde1fd9d29a6a74c44de3a29700759c1f962d3293b13dc03ce2a9db7c5b3
NHSDigital~immunisation-fhir-api~VNZ5YN.dockerbuild
43.9 KB
sha256:1788e75df26d39f06440be9379c0924ad140f0d1bd9c86fedb93cc65e2eb62dd
NHSDigital~immunisation-fhir-api~WML9HM.dockerbuild
43.6 KB
sha256:32baac438217446455a46e6f3feb1166f05ec92b85bc951e859e0a9b1d550acd
NHSDigital~immunisation-fhir-api~YMKUIG.dockerbuild
43.4 KB
sha256:43623fb6d2978c2bbe01acca7f60b388da3060b954738a5da8b7106f5ed3d39c
NHSDigital~immunisation-fhir-api~ZR600Q.dockerbuild
35.8 KB
sha256:3424e8f32634a3945ad93b4b34b5768cf67d0c010480f1439268e09a8fe46809
deploy-manifest-ack-backend-dev-pr-1427-1
638 Bytes
sha256:56c356bc657d4b5c3c853474db8a0cf2a5d9ce9bc3d9ab3336e38561ac8be6ab
deploy-manifest-backend-dev-pr-1427-1
623 Bytes
sha256:8cd25e8edbed48415f5308d230a20d769b8356954a16ed0def55d3d7f676d294
deploy-manifest-batch_processor_filter-dev-pr-1427-1
672 Bytes
sha256:981ac7d31a01f9d23736216e9769a05c7e5e98182aad5d5cd65198377e57286d
deploy-manifest-delta_backend-dev-pr-1427-1
641 Bytes
sha256:3a797f14e494f9a3d4d69d0ee6a8865dddc4541c72e31622c20e718044fe7aae
deploy-manifest-filenameprocessor-dev-pr-1427-1
655 Bytes
sha256:407f4a1f0e4c3d839c362b30c94233fcbc667c39e66a932eb3cf5e952d0071b7
deploy-manifest-id_sync-dev-pr-1427-1
627 Bytes
sha256:81564ddfa49d08dca8857466c4cf0170519ba3eec2d26dbfcfbd8f3bd28a672f
deploy-manifest-mesh_processor-dev-pr-1427-1
649 Bytes
sha256:e305754b663d07fd59c1847081beeee8d0d4ce0f99b7ef317f7256224b88a6ce
deploy-manifest-mns_publisher-dev-pr-1427-1
649 Bytes
sha256:2bd7bd11156549a773d6694c7551fc05102150625d9d0651247990d55e7f884c
deploy-manifest-mock_pds-dev-pr-1427-1
628 Bytes
sha256:c7e40ce77cbecdc0682e9c4ae76332a7569bdd3b799c2695c65821233f536f0e
deploy-manifest-recordforwarder-dev-pr-1427-1
650 Bytes
sha256:cf450bf8543e10148e17305765cac7c4945d14f365284ae9398d3b402772cb64
deploy-manifest-recordprocessor-dev-pr-1427-1
648 Bytes
sha256:6d1b38275ac332afcf632387b40ab8f0d8f8ec1f573cdee887b6a9f75e5b5190
deploy-manifest-redis_sync-dev-pr-1427-1
637 Bytes
sha256:8071bf2d79fec8177fc8ea7384738cc9400766938d33a3081fcb923c5050a964
dev-pr-1427-tfplan
252 KB
sha256:5bc83866bdaf469a7d0235851df1ab50f32771d0f1603216d4f429aaed571281