CCM-12896: Move generated Python types to digital-letters-events package

Author: gareth-allan

scripts/config/sonar-scanner.properties

@@ -8,7 +8,7 @@ sonar.tests=tests/, src/asyncapigenerator/tests, src/cloudeventjekylldocs/tests,
 sonar.test.inclusions=tests/**, src/**/tests/**, src/**/__tests__/**, lambdas/**/src/__tests__/**, utils/utils/src/__tests__/**, utils/sender-management/src/__tests__/**
 sonar.terraform.provider.aws.version=5.54.1
 sonar.cpd.exclusions=**.test.*
-sonar.coverage.exclusions=tests/**, src/**/tests/**, src/**/__tests__/**, **/*.dev.*, lambdas/**/src/__tests__/**, **/jest.config.ts, **/jest.config.cjs, scripts/**/*.*, docs/**/*.*, utils/utils/src/__tests__/**, src/asyncapigenerator/example_usage.py, src/asyncapigenerator/test_generator.py, src/eventcatalogasyncapiimporter/examples.py, src/digital-letters-events-python/**
+sonar.coverage.exclusions=tests/**, src/**/tests/**, src/**/__tests__/**, **/*.dev.*, lambdas/**/src/__tests__/**, **/jest.config.ts, **/jest.config.cjs, scripts/**/*.*, docs/**/*.*, utils/utils/src/__tests__/**, src/asyncapigenerator/example_usage.py, src/asyncapigenerator/test_generator.py, src/eventcatalogasyncapiimporter/examples.py, src/digital-letters-events/**
 
 sonar.python.coverage.reportPaths=src/asyncapigenerator/coverage.xml,src/cloudeventjekylldocs/coverage.xml,src/eventcatalogasyncapiimporter/coverage.xml
 sonar.javascript.lcov.reportPaths=lcov.info,src/cloudevents/coverage/lcov.info

src/digital-letters-events-python/.gitignore

@@ -1,2 +1,3 @@
 validators
 types
+models

src/digital-letters-events-python/README.md

@@ -1,16 +1,22 @@
 # digital-letters-events
 
+<!-- vale Vale.Terms = NO -->
 This package contains the automatically-generated code that the
-[typescript-schema-generator](../typescript-schema-generator/) tool produces.
+[typescript-schema-generator](../typescript-schema-generator/) and the
+[pydantic-model-generator](../pydantic-model-generator/) tools produce.
+<!-- vale Vale.Terms = YES -->
 
 The source files in this package should not be edited directly. If changes are
 required, update the schemas in the
 [src/cloudevents/domains](../cloudevents/domains) directory and use the
-`typescript-schema-generator` tool to regenerate them.
+`typescript-schema-generator` and `pydantic-model-generator` tools to regenerate
+them.
 
 ## Using this Package
 
-### Using Event Types
+### TypeScript
+
+#### Using Event Types
 
 The event types can be used by simply installing the
 `digital-letters-events` package as a dependency and then importing
@@ -51,7 +57,7 @@ const pdmResourceSubmittedEvent: PDMResourceSubmitted = {
   };
 ```
 
-### Using Event Validator Functions
+#### Using Event Validator Functions
 
 Validator functions for an event can be used by importing the default export
 from the relevant JS file in
@@ -74,3 +80,38 @@ if (isEventValid) {
 Note: You will need to make sure the
 [`allowJs`](https://www.typescriptlang.org/tsconfig/#allowJs) option is set in
 your package's `tsconfig.json` in order to import the JS files.
+
+### Python
+
+#### Using Event Models
+
+The Pydantic models can be used by installing the `digital-letters-events` package and importing the desired model:
+
+```python
+from digital_letters_events import PDMResourceSubmitted
+
+try:
+    # Validate and parse an event
+    event_data = {
+        "type": "uk.nhs.notify.digital.letters.pdm.resource.submitted.v1",
+        "source": "/nhs/england/notify/staging/dev-647563337/data-plane/digitalletters/pdm",
+        "dataschema": "https://notify.nhs.uk/cloudevents/schemas/digital-letters/2025-10-draft/data/digital-letters-pdm-resource-submitted-data.schema.json",
+        "specversion": "1.0",
+        "id": "0249e529-f947-4012-819e-b634eb71be79",
+        "subject": "pdm-resource-123",
+        "time": "2025-12-11T10:00:00Z",
+        "data": {
+            "something": "example value"
+        }
+    }
+
+    # Create and validate the event
+    event = PDMResourceSubmitted(**event_data)
+
+    # Access validated fields
+    print(event.id)
+    print(event.type)
+    print(event.data.something)
+except Exception as e:
+    print(e)
+```

src/digital-letters-events/.gitignore

@@ -1,6 +1,6 @@
 # Variables
 SCHEMA_SRC_DIR := ../../schemas/digital-letters/2025-10-draft/events
-OUTPUT_DIR := ../digital-letters-events-python/models
+OUTPUT_DIR := ../digital-letters-events/models
 SCRIPTS_DIR := scripts
 
 # Default target

src/digital-letters-events/README.md

@@ -29,7 +29,7 @@ This will:
 
 - Read all JSON event schemas from `schemas/digital-letters/2025-10-draft/events/`
 - Generate Pydantic v2 models using `datamodel-code-generator`
-- Output the models to `../digital-letters-events-python/models/`
+- Output the models to `../digital-letters-events/models/`
 
 ### Configuration
 
@@ -44,12 +44,12 @@ The generator can be configured through:
 <!-- vale Vale.Terms = NO -->
 <!-- vale Vale.Avoid = NO -->
 Generated models are placed in the
-[digital-letters-events-python](../digital-letters-events-python/) package:
+[digital-letters-events](../digital-letters-events/) package:
 <!-- vale Vale.Terms = YES -->
 <!-- vale Vale.Avoid = YES -->
 
-- `../digital-letters-events-python/models/` - Individual Pydantic model files
-- `../digital-letters-events-python/models/__init__.py` - Combined index for easy imports
+- `../digital-letters-events/models/` - Individual Pydantic model files
+- `../digital-letters-events/models/__init__.py` - Combined index for easy imports
 
 ## Testing