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
@@ -125,8 +131,9 @@ For detailed instructions on running individual Lambdas, refer to the README.md
125
131
Steps:
126
132
1. Set the python version in the folder with the code used by lambda for example `./backend` (see [lambdas](#lambdas)) folder.
127
133
```
128
-
pyenv local 3.10.16 # Set version in backend (this creates a .python-version file)
134
+
pyenv local 3.11.13 # Set version in backend (this creates a .python-version file)
129
135
```
136
+
Note: consult the lambda's `pyproject.toml` file to get the required Python version for this lambda. At the time of writing, this is `~3.10` for the batch lambdas and `~3.11` for all the others.
130
137
131
138
2. Configure poetry
132
139
```
@@ -203,4 +210,13 @@ The root (`immunisation-fhir-api`) should point to `/mnt/d/Source/immunisation-f
203
210
## Verified commits
204
211
Please note that this project requires that all commits are verified using a GPG key.
205
212
To set up a GPG key please follow the instructions specified here:
## AWS configuration: Getting credentials for AWS federated user account
217
+
218
+
In the 'Access keys' popup menu under AWS Access Portal:
219
+
220
+
**NOTE** that AWS's 'Recommended' method of getting credentials **(AWS IAM Identity Center credentials)** will break mocking in unit tests; specifically any tests calling `dynamodb_client.create_table()` will fail with `botocore.errorfactory.ResourceInUseException: Table already exists`.
221
+
222
+
Instead, use **Option 2 (Add a profile to your AWS credentials file)**.
0 commit comments