Repository navigation
CCM-24327: Monitor same day letter supplier SLA breaches - #731
Draft
RossFaulds171 wants to merge 1 commit into
Draft
RossFaulds171 wants to merge 1 commit into
RossFaulds171 wants to merge 1 commit into
Conversation
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Initial creation of state machine, including lambda to copy the supplier config dynamodb into json files separated by entity type into an S3 bucket.
Creates dummy lambdas for standard, and sameday SLA breach lambdas to be implemented in later changes.
New state machine for letter supplier SLA breaches.
New lambda for extracting supplier config for later population into athena
New dummy lambda to act as a placeholder for same day sla breaches
New dummy lambda to act as a placholder for standard letter sla breaches
Context
A recent issue arose where a large number of letters had not been fulfilled within the SLA period, we need to be able
to see metrics showing how many letters are in breach so that we can proactively deal with breaches in a timely manner
Type of changes
Checklist
DT3-Specific 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.