You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version release history can be found ot https://github.com/NHSDigital/eps-prescription-status-update-api/releases.
9
-
We use eslint convention for commit messages for commits to main branch. Descriptions for the types of changes in a release can be found in the [contributing guidelines](./CONTRIBUTING.md)
8
+
Version release history can be found ot https://github.com/NHSDigital/eps-prescription-status-update-api/releases.
9
+
We use eslint convention for commit messages for commits to main branch. Descriptions for the types of changes in a release can be found in the [contributing guidelines](./CONTRIBUTING.md)
10
10
Deployment history can be found at https://nhsdigital.github.io/eps-prescription-status-update-api/
11
11
12
12
## Introduction
@@ -20,6 +20,7 @@ This is the AWS layer that provides an API for EPS Prescription Status Update.
20
20
-`packages/capabilityStatement` Returns a static capability statement.
21
21
-`packages/cpsuLambda` Handles updating prescription status using a custom format.
22
22
-`packages/nhsNotifyLambda` Handles sending prescription notifications to the NHS Notify service.
23
+
-`packages/postDatedLambda` Handles business logic for post-dated prescriptions getting notifications \[deprecated\].
23
24
-`packages/nhsNotifyUpdateCallback` Handles receiving notification updates from the NHS Notify service.
24
25
-`packages/checkPrescriptionStatusUpdates` Validates and retrieves prescription status update data.
25
26
-`packages/gsul` Expose data owned by PSU but needed by [PfP](https://github.com/NHSDigital/prescriptionsforpatients)
@@ -56,9 +57,9 @@ The contents of this repository are protected by Crown Copyright (C).
56
57
57
58
## Development
58
59
59
-
It is recommended that you use visual studio code and a devcontainer as this will install all necessary components and correct versions of tools and languages.
60
-
See https://code.visualstudio.com/docs/devcontainers/containers for details on how to set this up on your host machine.
61
-
There is also a workspace file in .vscode that should be opened once you have started the devcontainer. The workspace file can also be opened outside of a devcontainer if you wish.
60
+
It is recommended that you use visual studio code and a devcontainer as this will install all necessary components and correct versions of tools and languages.
61
+
See https://code.visualstudio.com/docs/devcontainers/containers for details on how to set this up on your host machine.
62
+
There is also a workspace file in .vscode that should be opened once you have started the devcontainer. The workspace file can also be opened outside of a devcontainer if you wish.
62
63
The project uses [SAM](https://aws.amazon.com/serverless/sam/) to develop and deploy the APIs and associated resources.
63
64
64
65
All commits must be made using [signed commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
@@ -239,8 +240,8 @@ Workflows are in the `.github/workflows` folder:
239
240
240
241
### Github pages
241
242
242
-
Github pages is used to display deployment information. The source for github pages is in the gh-pages branch.
243
-
As part of the ci and release workflows, the release tag (either the short commit SHA or release tag) is appended to \_data/{environment}\_deployments.csv so we have a history of releases and replaced in \_data/{environment}\_latest.csv so we now what the latest released version is.
243
+
Github pages is used to display deployment information. The source for github pages is in the gh-pages branch.
244
+
As part of the ci and release workflows, the release tag (either the short commit SHA or release tag) is appended to \_data/{environment}\_deployments.csv so we have a history of releases and replaced in \_data/{environment}\_latest.csv so we now what the latest released version is.
244
245
There are different makefile targets in this branch. These are
245
246
246
247
-`run-jekyll` - runs the site locally so changes can be previewed during development
0 commit comments