CCM-15256: invalid attachment received diagram#280
Conversation
| description: A codified reason for the status of the message | ||
| examples: | ||
| - "FAILURE001" | ||
| - "DL_CLIV_002" |
There was a problem hiding this comment.
Changed to a realistic example
| description: The failure code indicating the reason for the message being invalid | ||
| examples: | ||
| - "LOCALID_HEADER_MISSING" | ||
| - "DL_CLIV_001" |
There was a problem hiding this comment.
Changed to a realistic example
| nodejs 24.10.0 | ||
| pre-commit 3.6.0 | ||
| python 3.14.0 | ||
| ruby 3.2.0 |
There was a problem hiding this comment.
Added this as I'd got the wrong version of ruby and my build didn't work. This seems to be the version we need but wasn't defined here
gareth-allan
left a comment
gareth-allan
left a comment
There was a problem hiding this comment.
Looks good, but just one comment about a filename.
There was a problem hiding this comment.
This aligns with the file-safe.md and file-quarantined.md files, but I've just noticed that most of the other events are in files named -. E.g the uk.nhs.notify.digital.letters.queue.digital.letter.read.v1 event is in a file named queue-digital-letter-read. We also already have print-letter-transitioned.md.
Should this file be print-invalid-attachment-received.md?
2 participants
Description
Context
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.