-
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
🔱 Productionise Glue Copy Metadata script #6133
Labels
spike
investigation, discovery into a thing
Comments
tom-webber
added a commit
that referenced
this issue
Nov 26, 2024
This PR is being tracked as part of #6133 Depends on ministryofjustice/modernisation-platform-environments#8812 Uses a clearer name for the role assumed by the CaDeT runner
This was referenced Nov 26, 2024
tom-webber
added a commit
that referenced
this issue
Nov 27, 2024
This PR is being tracked as part of #6133 Depends on ministryofjustice/modernisation-platform-environments#8812 Uses a clearer name for the role assumed by the CaDeT runner
tom-webber
added a commit
that referenced
this issue
Nov 27, 2024
This PR is being tracked as part of #6133 Depends on ministryofjustice/modernisation-platform-environments#8812 Uses a clearer name for the role assumed by the CaDeT runner
This was referenced Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Follows on from #5859
Currently, the python script which copies metadata across accounts is running locally. We need to decide and agree on where it's best to deploy it and conditions under which to run it.
Proposal
Spike requirements
Data Engineer 3 das
Definition of Done
The text was updated successfully, but these errors were encountered: