-
Notifications
You must be signed in to change notification settings - Fork 1
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
[ETL-558] Decouple S3 to JSON workflow from JSON to Parquet workflow #83
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥 LGTM here! Thanks for being intentional about not having the development pipelines run on a daily basis.
templates/glue-workflow.j2
Outdated
WorkflowName: !Ref JsonToParquetWorkflow | ||
|
||
JsontoParquetTrigger: | ||
Condition: !Not IsMainNamespace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird... it's saying: Every Condition member must be a string.
. Is that due to this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the error log this might help root out the issue and let us test as changes are made:
aws cloudformation validate-template --template-body templates/glue-workflow.j2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. CFN is not very flexible. I fixed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BryanFauble It seems like that command only checks if the template is valid YAML and not whether it's semantically correct? In any case, I use Jinja in the template so that command fails immediately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With all pipelines passing the changes LGTM!
The important changes happen in templates/glue-workflow.j2. This PR splits our workflow into two workflows:
main
namespace (so as to not waste resources triggering the pipeline every day on our development stacks).