VED-1138: Allow create action to reinstate deleted records #2340
Thomas-Boylepr-deploy-and-test.yml
on: pull_request
run-quality-checks
/
Lint specification
19s
run-quality-checks
/
Lint Python projects
32s
run-quality-checks
/
Lint Terraform projects
6s
run-quality-checks
/
Test Coverage and SonarCloud
4m 36s
Matrix: deploy-pr-backend / deploy-lambda-images
Matrix: run-e2e-automation-tests
Annotations
11 warnings
|
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 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 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 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 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/
|
|
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 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 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 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
NHSDigital~immunisation-fhir-api~AZSVX7.dockerbuild
|
69 KB |
sha256:d1111b6618af794632357a90e268e508bd82a33cbf51184419e772632a9a8ce0
|
|
|
NHSDigital~immunisation-fhir-api~DTZ0GA.dockerbuild
|
68.4 KB |
sha256:429cda1ddd63bac837f5269de3ce91a96e63384eb2aafc94c52782f719899d14
|
|
|
NHSDigital~immunisation-fhir-api~GUN2P9.dockerbuild
|
67.5 KB |
sha256:2c699137b0663d6d66f491e003c2dad1633a1f6a47625bbc35c4980cf0e84756
|
|
|
NHSDigital~immunisation-fhir-api~HRI5CW.dockerbuild
|
67.8 KB |
sha256:8160933fb7a1d5fefa6120871c7a523f1b2f56f2aa9ec555ff8adfe9f4e7bb55
|
|
|
NHSDigital~immunisation-fhir-api~IRSCW9.dockerbuild
|
45.9 KB |
sha256:da3426862747345f02a69725bba07230e40856628084a2c6f7daac0c819cfb95
|
|
|
NHSDigital~immunisation-fhir-api~JFY5UX.dockerbuild
|
68 KB |
sha256:39f749594b81d8bccb759fa3f25052614184ab37ef7a775e585cf65541ba0c44
|
|
|
NHSDigital~immunisation-fhir-api~LMNFAK.dockerbuild
|
68.6 KB |
sha256:2833742e482d5036f168270be62515a65ed134d112aabef9f24386d5b6ee5f7d
|
|
|
NHSDigital~immunisation-fhir-api~PYT163.dockerbuild
|
67.5 KB |
sha256:7697c97843d0d3aebcf7adc86c7c66e244315371bca290298079e7c21bea4282
|
|
|
NHSDigital~immunisation-fhir-api~S5IPWA.dockerbuild
|
69.8 KB |
sha256:21aad4a799dde5d2438b2e14a35776ff98136da2d041c9c0329f8250580202e5
|
|
|
NHSDigital~immunisation-fhir-api~UL277U.dockerbuild
|
68.3 KB |
sha256:71037f0759f421087c7b615932b33f6f98ecc43e6e31a3577889dd8298b3147f
|
|
|
NHSDigital~immunisation-fhir-api~VI78AU.dockerbuild
|
66.8 KB |
sha256:886dbe62b2f2d30ff7283a884f340af7e29e38defe708ad1550e96fbcb9aab71
|
|
|
deploy-manifest-ack-backend-dev-pr-1435-1
|
624 Bytes |
sha256:92eb8d5bd341ed1ed1cfb5072f8b8ae2e596a955b5731155b3835c795743be78
|
|
|
deploy-manifest-backend-dev-pr-1435-1
|
609 Bytes |
sha256:dc75bf553a400b285e153fcc43cebd595a2d4827e283a9e55249beb4d858a1df
|
|
|
deploy-manifest-batch_processor_filter-dev-pr-1435-1
|
654 Bytes |
sha256:f2f8e934c04888c0f59ac9002b9d3e3dc6d644af0e8a8eb9e03e678f1c6f1cfb
|
|
|
deploy-manifest-delta_backend-dev-pr-1435-1
|
627 Bytes |
sha256:c3a61b1eae54989df10f058fb2b90cfd464671b3c5f42d9ebfa2f7e1b982c093
|
|
|
deploy-manifest-filenameprocessor-dev-pr-1435-1
|
636 Bytes |
sha256:e4b56e4100425f75ba6760d50f13d6f01c16ef12b3b3f028f586782383e73bf4
|
|
|
deploy-manifest-id_sync-dev-pr-1435-1
|
610 Bytes |
sha256:1b1cbf36f5dce63e8a2bd7129971bffe6d6531f14f612f04417052e664a11bbe
|
|
|
deploy-manifest-mesh_processor-dev-pr-1435-1
|
632 Bytes |
sha256:1865ffdf1b0a830c2cf1a3a685b44f801bbf2c565dd0d8a38523532dda26d71a
|
|
|
deploy-manifest-mns_publisher-dev-pr-1435-1
|
630 Bytes |
sha256:1fdc3bea60d38caa08fa30ddceb5da61e98d99e24198d9983f073b69a8180db6
|
|
|
deploy-manifest-recordforwarder-dev-pr-1435-1
|
630 Bytes |
sha256:8cfeea9ff9f0afeecb521057257b414167a5cd44b6864342fd8895b808020930
|
|
|
deploy-manifest-recordprocessor-dev-pr-1435-1
|
629 Bytes |
sha256:73810091145ef771d4d5f6b6a20d90825d1d803e96f39539b1af11880ed70baa
|
|
|
deploy-manifest-redis_sync-dev-pr-1435-1
|
619 Bytes |
sha256:43eecade3bc5da4971451226c52a87994dcab43cbfd0d4da5c051552fe745bd6
|
|
|
dev-pr-1435-internal-dev-e2e-test-output
|
558 KB |
sha256:6967d3e3c73bdea89e0f7bb32036bc403ef6257fbda8caf5a49a1e9f12877f94
|
|
|
dev-pr-1435-internal-dev-sandbox-e2e-test-output
|
9.48 KB |
sha256:6d05614a961540ec8143297c9c628475fcf5e5c98806fd5fde6cc5668db04b42
|
|
|
dev-pr-1435-tfplan
|
98.1 KB |
sha256:979aa4e224934d64a1d87dc23cafc4d964edd2872311c241f227c1b0be43b902
|
|