Creating and updating lambda READMEs#540
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #540 +/- ##
=======================================
Coverage 95.78% 95.78%
=======================================
Files 46 46
Lines 2372 2372
=======================================
Hits 2272 2272
Misses 100 100 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
nickclyde
left a comment
There was a problem hiding this comment.
Awesome, thanks for adding these Rob!!
| ```text | ||
| S3_BUCKET | ||
| TTC_INPUT_PREFIX | ||
| TTC_OUTPUT_PREFIX | ||
| AUGMENTED_EICR_PREFIX | ||
| AUGMENTATION_METADATA_PREFIX | ||
| ``` |
There was a problem hiding this comment.
I think this env var list is missing AWS_REGION
| - Loading the original eICR XML from S3. | ||
| - Parsing nonstandard code translations from TTC output. | ||
| - Running eICR augmentation through the core augmentation package. | ||
| - Managing a S3-derived persistence ID for the augmented document and set IDs. |
There was a problem hiding this comment.
I found "and set IDs" a little ambiguous on first read. I believe this is referring to the eICR setId/versionNumber header elements that EICRAugmenter rewrites deterministically from the persistence_id seed, but it could also be read as "the augmented document and the set IDs (plural)." Could we phrase it as something like "Seeding deterministic eICR document IDs (id, setId, versionNumber) from the persistence ID" so it's clearer what's being managed?
|
|
||
| ## Overview | ||
|
|
||
| 🚧 Under Construction 🚧 |
There was a problem hiding this comment.
Now that this README has substantive content, should we remove the "Under Construction" banner? Same question for the lambda-handler README
| For example: | ||
|
|
||
| ```text | ||
| TTCInput/2026/01/01/0026b704-f510-4494-8d21-11d27217d96e |
There was a problem hiding this comment.
Nit: TTCInput/ is the old prefix we had, the new defaults are TextToCodeSubmissionV2/, ValidationResponseV2/, TTCAugmentationMetadataV2/, etc.
| - `create_s3_client` | ||
| - `get_file_content_from_s3` | ||
| - `put_file` | ||
| - `check_s3_object_exists` | ||
| - `get_eventbridge_data_from_s3_event` | ||
| - `get_persistence_id` |
There was a problem hiding this comment.
Nit: get_eventbridge_data_from_s3_event and get_persistence_id aren't really S3 helpers, they're EventBridge/key-parsing helpers that happen to be used alongside S3. Would it be worth renaming this section to something broader like "S3 and Event Helpers"?
|
|
||
| ## Logging | ||
|
|
||
| Every TTC invocation logs the record count at the start of processing. |
There was a problem hiding this comment.
Suggestion for a little more specificity: "Every TTC invocation logs the record count at the start. For each record, the Lambda logs the event bucket, triggering object key, and derived persistence ID as structured fields..."
| Run the package tests with: | ||
|
|
||
| ```bash | ||
| uv run pytest packages/index-lambda/tests |
There was a problem hiding this comment.
You can do this with the just command with just all unit packages/index-lambda/tests
| uv run pytest packages/index-lambda/tests | |
| just all unit packages/index-lambda/tests |
| Run the package tests with: | ||
|
|
||
| ```bash | ||
| uv run pytest packages/lambda-handler/tests |
There was a problem hiding this comment.
| uv run pytest packages/lambda-handler/tests | |
| just test all packages/lambda-handler/tests |
| Run the package tests with: | ||
|
|
||
| ```bash | ||
| uv run pytest packages/text-to-code-lambda/tests |
There was a problem hiding this comment.
| uv run pytest packages/text-to-code-lambda/tests | |
| just test all packages/text-to-code-lambda/tests |
| @@ -1,19 +1,116 @@ | |||
| # DIBBs Index Initialization | |||
|
|
|||
| **General disclaimer** This repository was created for use by CDC programs to collaborate on public health related projects in support of the [CDC mission](https://www.cdc.gov/about/cdc/#cdc_about_cio_mission-our-mission). GitHub is not hosted by the CDC, but is a third party website used by CDC and its partners to share information and collaborate on software. CDC use of GitHub does not imply an endorsement of any one particular service, product, or enterprise. | |||
There was a problem hiding this comment.
Why remove the Markdown link?
| # DIBBs Augmentation | ||
| # DIBBs Augmentation Lambda | ||
|
|
||
| **General disclaimer** This repository was created for use by CDC programs to collaborate on public health related projects in support of the [CDC mission](https://www.cdc.gov/about/cdc/#cdc_about_cio_mission-our-mission). GitHub is not hosted by the CDC, but is a third party website used by CDC and its partners to share information and collaborate on software. CDC use of GitHub does not imply an endorsement of any one particular service, product, or enterprise. |
There was a problem hiding this comment.
Does this disclaimer need to be in each package's readme?
| Run the package tests with: | ||
|
|
||
| ```bash | ||
| uv run pytest packages/augmentation-lambda/tests |
There was a problem hiding this comment.
| uv run pytest packages/augmentation-lambda/tests | |
| just test all packages/augmentation-lambda/tests |
Description
Just updating / initializing README for the lambdas.
Not sure if other modules like
text-to-code,augmentation, andvalidation, etc. Happy to make a ticket for that work. I actually don't know if we've chatted about if/how we want readable docs for the lambdas given that we aren't currently pursuing API stuff. Figured the lambdas at least will still be helpful to have more granular.Anyway, maybe food for thought for an eng sync and/or parking lot.
Related Issues
Closes #[Link any related issues or tasks from your project management system.]
Additional Notes
[Add any additional context or notes that reviewers should know about.]
<--------------------- REMOVE THE LINES BELOW BEFORE MERGING --------------------->
Checklist
Please review and complete the following checklist before submitting your pull request:
Checklist for Reviewers
Please review and complete the following checklist during the review process: