-
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
Labels
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! |
Gary-H9
changed the title
✉ Migrate JML Lambda to AP Compute Account
λ: Migrate JML Lambda to AP Compute Account
Jan 8, 2025
Gary-H9
changed the title
λ: Migrate JML Lambda to AP Compute Account
λ: Migrate JML Lambda to Jan 8, 2025
analytical-platform-data-production
This was referenced Jan 8, 2025
TODO: Another PR later to remove the unneeded ones. |
This was referenced Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: