-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
λ: Migrate JML Lambda to analytical-platform-data-production
#6517
Comments
Created a quick PR to remove the Lambda function. Will review tomorrow to make sure nothing is missed. |
Turns out this is a duplicate of this ticket. 🤕 Editing this one appropriately as I've been working in here before closing the previous one - sorry Jacob! |
analytical-platform-data-production
TODO: Another PR later to remove the unneeded ones. |
Errored on apply, will rectify on Monday. |
Re-approached this piece of work since consuming the legacy ECR introduced other difficulties we hadn't foreseen when writing this ticket. New approach is to create a new ECR in As part of this piece of work I've also added a maintenance issue so this doesn't fall out of line again in future. TODO: Rename the lambda function itself once everything is working. |
Refactor PR |
Release successful, confirmed in AWS console on TODO: Update secrets. |
The purpose of this story is to migrate the lambda function:
data_platform_jml_extract
in thedata-platform-apps-and-tools-production
AWS accountto the Analytical Platform Compute account.analytical-platform-compute-production
analytical-platform-data-production
.The code for this lives in the modernisation-platform-environments repository. For example here.
Notes:
Approach:
One PR to remove from Apps and Tools ProductionThis will be deleted as part of the account being deleted.The text was updated successfully, but these errors were encountered: