Skip to content

VED-1252: Site & Route - In case of multiple lists of valid system, it's storing only 1st list and ignores rest all lists in Imms Event table #2375

VED-1252: Site & Route - In case of multiple lists of valid system, it's storing only 1st list and ignores rest all lists in Imms Event table

VED-1252: Site & Route - In case of multiple lists of valid system, it's storing only 1st list and ignores rest all lists in Imms Event table #2375

Triggered via pull request April 27, 2026 09:56
Status Success
Total duration 35m 24s
Artifacts 25

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
17s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
30s
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
3m 59s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
40s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
4m 7s
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Fit to window
Zoom out
Zoom in

Annotations

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

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~57EXVU.dockerbuild
68.7 KB
sha256:ddc8ec2a7c5705c3bc3fc717ac00f027b1186ab5f5f6e1dce2edbd1e4de06bdd
NHSDigital~immunisation-fhir-api~M90K0J.dockerbuild
67.7 KB
sha256:70a6283f4fdcd7ce3594e5d121130385cee77964c456d44e98ef9f58a5f719fd
NHSDigital~immunisation-fhir-api~O5XXEL.dockerbuild
66.3 KB
sha256:d12c271675038cb50569db439a6f2bff21aec8b8aa7ae87ff934d1c01cb80a04
NHSDigital~immunisation-fhir-api~OIGMB7.dockerbuild
68.7 KB
sha256:5db62eacd91a8a7485757b40f376c4a8bf0afa562c0b1fb346bb9147946d1674
NHSDigital~immunisation-fhir-api~OJKHHC.dockerbuild
67.6 KB
sha256:7b2918dc39be59b1a9edfedee44ad8eb4d98234204e0f470aee6eee723f1e454
NHSDigital~immunisation-fhir-api~PRQL2W.dockerbuild
70.7 KB
sha256:691057cd47e19247b55e1c6219300c8b0006fddc6da41fa73d82d0d2f01f8098
NHSDigital~immunisation-fhir-api~Q6VXYU.dockerbuild
68.8 KB
sha256:61df6d798dac30a98e5729a1afb9fce932995fcfb2a70528f9a489c6e1b7d7b3
NHSDigital~immunisation-fhir-api~S2PPYF.dockerbuild
69.6 KB
sha256:3dd7f6958589efedba716c1f09041b65610804e1107e5c271e735434e885c04d
NHSDigital~immunisation-fhir-api~VNE1IC.dockerbuild
70.3 KB
sha256:4cf408122872c9127e63fc8fd1cbab7044b3acc197d53dd2edd76c7bb02a956c
NHSDigital~immunisation-fhir-api~VUVGZW.dockerbuild
68.4 KB
sha256:b8dbeabe93f59b7d86f500748b1e6e46a17b776a34d05d32441255da4295ce1d
NHSDigital~immunisation-fhir-api~Z0QW02.dockerbuild
71.4 KB
sha256:8b5411d3b46c27316c2352f26f2595045a08c11910199a769fdafd9ddbd9ccc6
deploy-manifest-ack-backend-dev-pr-1446-1
626 Bytes
sha256:ac23dd3ac7337be8e8297fb38448daa65ccc5a3699b41fa4855384de982026b4
deploy-manifest-backend-dev-pr-1446-1
610 Bytes
sha256:c7edb2c02700900d761125031d9c7ef5247a85eab229c1f31efab9a67d5f34e3
deploy-manifest-batch_processor_filter-dev-pr-1446-1
658 Bytes
sha256:e70fc0bf6b9817049dbd01c0b9b7280245f98f908185cc27c6b94e4f9aa077f9
deploy-manifest-delta_backend-dev-pr-1446-1
629 Bytes
sha256:095b823282066b9897d4caecef8ed5437346ef791f79f4d0790e5bad1eea941c
deploy-manifest-filenameprocessor-dev-pr-1446-1
640 Bytes
sha256:3f3dc46a4e517e678e85155a7e0f0561e92fa08ac209019b8ea3dfd40fab0216
deploy-manifest-id_sync-dev-pr-1446-1
614 Bytes
sha256:5aea94df1332380d5a642caabfcea714f55e7d0650e95a7568dfd1fde59090fb
deploy-manifest-mesh_processor-dev-pr-1446-1
633 Bytes
sha256:bfca763121b59ca0d620c293df0b651342b82335fcd3f32b6d2d95073b8fab30
deploy-manifest-mns_publisher-dev-pr-1446-1
630 Bytes
sha256:2b34a7ee5b6b8ccb233b721d3f769b4775fd125a6b0991ef6a89f0203956843a
deploy-manifest-recordforwarder-dev-pr-1446-1
632 Bytes
sha256:c00dee22a4766d7e6de8052dcfa913c0ebf2aa977dfa126d4650ba56fc6baf1b
deploy-manifest-recordprocessor-dev-pr-1446-1
634 Bytes
sha256:f9715f4a4cf1ed43ffa932e36e0b2a399cc26207e8dd279025657c240d4cc86d
deploy-manifest-redis_sync-dev-pr-1446-1
622 Bytes
sha256:46d07784317b9f1158f4cacd28cd0eddbd93d502271ccf0a6af1201defda3c86
dev-pr-1446-internal-dev-e2e-test-output
558 KB
sha256:4266e4c8e5c7098c319402d36cc079c03ccff0c509f3e6bbd736ea7a537dd4a3
dev-pr-1446-internal-dev-sandbox-e2e-test-output
9.48 KB
sha256:9eee955e099e2daf8d93ef4a296569fe79042a6639ace85182e7a3b9d13eabcb
dev-pr-1446-tfplan
98.3 KB
sha256:6bd83dee24c371243202255ea6718d1cad5e3e8f0a1d6c3b6d2b2fe6fc7e658d