Skip to content

VED-1138: Allow create action to reinstate deleted records #2381

VED-1138: Allow create action to reinstate deleted records

VED-1138: Allow create action to reinstate deleted records #2381

Triggered via pull request April 28, 2026 08:42
Status Success
Total duration 24m 45s
Artifacts 25

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
24s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
28s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
7s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
3m 55s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
59s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
1m 51s
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
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 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 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 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 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 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 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 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~4NV5O9.dockerbuild
46 KB
sha256:d9a56913fd73680f17ddbb3674e5f153c8655f759c218359a87532810ab9e63d
NHSDigital~immunisation-fhir-api~I3TNYU.dockerbuild
47.6 KB
sha256:df46e4e11a5413423b37cb38ed5bddb9773cedac79acda5b6857f09cae6b7cda
NHSDigital~immunisation-fhir-api~JAZOAN.dockerbuild
45.9 KB
sha256:f374d8dffb0e0ce4183ec369af1e07d2d16a5af37693ccf21f3eb3a76c6fd5de
NHSDigital~immunisation-fhir-api~K98PNP.dockerbuild
45.1 KB
sha256:2f5fe031f2ee269a8d0feaa74cdd296fb9794c213864fe54b579e181365987ff
NHSDigital~immunisation-fhir-api~KRRE60.dockerbuild
46.3 KB
sha256:34776559d4db5ebae1f29a9255cef029c37780afa13b3a5e3291405fa47c2e61
NHSDigital~immunisation-fhir-api~KWHNTZ.dockerbuild
45.5 KB
sha256:05bc08c26daa69316c604d90248a5a022d96f613997c306dcfbddd34d0660b62
NHSDigital~immunisation-fhir-api~NBXIF0.dockerbuild
46 KB
sha256:955d9eef186da8582ce0284579a82d20fe868aeb20e7fb46749917681d8172d9
NHSDigital~immunisation-fhir-api~OH2UYN.dockerbuild
45.4 KB
sha256:63ac02fa66a132710f1fe23f817179a3f4d5a73509a4f2f36ec265dc57689593
NHSDigital~immunisation-fhir-api~QA3RDA.dockerbuild
46.4 KB
sha256:1fcf6ea9a46ef13923e868f28852a6231438838ed44fcd5ceefdab6a6eb18a4c
NHSDigital~immunisation-fhir-api~VZWFYK.dockerbuild
46.2 KB
sha256:17857ddccf38aa611806349869e257d12e119813905b048b58febbe7d6b946b6
NHSDigital~immunisation-fhir-api~XL69NH.dockerbuild
47.4 KB
sha256:67bb59ffc1eff5f277cbef93cbc79e3a2f2b457f072cf02a1a1e46fafcbe274c
deploy-manifest-ack-backend-dev-pr-1435-1
627 Bytes
sha256:f376a6e979079f0d26b119fd5ecbc9392eada0f583b19ba6d5586d90627d3d61
deploy-manifest-backend-dev-pr-1435-1
611 Bytes
sha256:9f67fc1dee13d32d69773d8ae50cac2510ef871b25685c283a53def602607252
deploy-manifest-batch_processor_filter-dev-pr-1435-1
657 Bytes
sha256:3bf90fc79725fda70f2cea26831fd74c1a30ed71617f30401a49d4f7967a014c
deploy-manifest-delta_backend-dev-pr-1435-1
628 Bytes
sha256:67a68289f02a5e03d19c471bca8abecf53522719fb7c8a42c53f23591a65e26d
deploy-manifest-filenameprocessor-dev-pr-1435-1
639 Bytes
sha256:de8bac683ec7611b2f50138bdad2eb56678d8dcdcb05548f049b92ce456f6e65
deploy-manifest-id_sync-dev-pr-1435-1
613 Bytes
sha256:18be05212b26c90d0dfa44ee39bad8c73b03ee89b74dfdaf551a53e04038ccb0
deploy-manifest-mesh_processor-dev-pr-1435-1
633 Bytes
sha256:c3d551d0f7fd3a30e59d2bce83f452c26dffd1b0fa2a00faf2094551abf2bfe5
deploy-manifest-mns_publisher-dev-pr-1435-1
630 Bytes
sha256:087a3e91b9612bc6f841e458130e92a3d18d055d30620a244a5074315d86d3d1
deploy-manifest-recordforwarder-dev-pr-1435-1
632 Bytes
sha256:1f134cc157daede9d074e1ee896d912b189521fc29ce5e9f1ef23586896359ca
deploy-manifest-recordprocessor-dev-pr-1435-1
632 Bytes
sha256:5987622206dafd59a9d3c8ae1bac34819b2b218a9430b43b4e1c45841fad0a72
deploy-manifest-redis_sync-dev-pr-1435-1
621 Bytes
sha256:d8a608c4f255a69eacef814ce26b4d649e967dffd42b40fa1427af0208ed3ba6
dev-pr-1435-internal-dev-e2e-test-output
558 KB
sha256:9fa16a32e58f49d4d29e0019d37ef9125d58eb9345a9c49e0da51bf529e2d9a2
dev-pr-1435-internal-dev-sandbox-e2e-test-output
9.47 KB
sha256:e6ff54e68ae1094750f555163194aabbf4122dec5c7f510c6a163a5a41984c61
dev-pr-1435-tfplan
244 KB
sha256:e8a5efbdd432d4d6dc7e645fe903d6586a9eb8e9245d7edef6a76e9d33cbb25e