You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
We have multiple CloudFront distributions (across a couple different AWS accounts). It seems like the job definition file only allows a single job per service type. It seems like allowing the job definition file to be overridden could help both those situations.
You've got a good point here - easiest thing is probably just adding a line as you mentioned, but in reality the glue_jobs.json file should probably just be a list of job definitions rather than a dictionary with the key being hard-coded to the service type.
I've been experimenting with Glue blueprints as a replacement for big chunks of this script so will take that into consideration.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have multiple CloudFront distributions (across a couple different AWS accounts). It seems like the job definition file only allows a single job per service type. It seems like allowing the job definition file to be overridden could help both those situations.
Like maybe changing this line https://github.com/awslabs/athena-glue-service-logs/blob/master/Makefile#L6 to:
JOB_DEFINITION_FILE?=scripts/glue_jobs.json
?The text was updated successfully, but these errors were encountered: