DMP-4683: Populate retention_policy_type_heritage_mapping table #2506
Conversation
This file contains 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
Ben-Edwards-cgi
requested review from
davet1985,
jackmaloney,
cakeben,
NickAzureDevops,
endakelly and
lukaszk-hmcts
and removed request for
a team
jackmaloney
approved these changes
Jan 29, 2025
|
Do not merge until 72.3/4 change is merged |
karen-hedges
approved these changes
Jan 31, 2025
…o V1_442__populate_ retention_policy_type_heritage_mapping.sql
hmcts-jenkins-cnp
bot
added
ns:darts-modernisation
prd:darts
rel:darts-api-pr-2506
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Links
Change description
Create a flyway script to populate the retention_policy_type_heritage_mapping table. See attached for required data.
Note this is dependant on completion of the V42.3/42.4 datamodel updates.
+AC1: Verify content of the retention_policy_type_heritage_mapping table+
{}Given{}: The flyway script created by this ticket has been executed in staging
{}When{}: I inspect the retention_policy_type_heritage_mapping table
{}Then{}: The table should exactly reflect the data provided in the attachment
Does this PR introduce a breaking change? (check one with "x")