Conversation
anayeaye
left a comment
There was a problem hiding this comment.
These changes look good--was the main update just to the airflow base url?
| else | ||
| echo "$collection_id failed to publish ❌" | ||
| exit 1 | ||
| fi |
There was a problem hiding this comment.
I can delete this file once this PR is reviewed!
| status_code = _extract_http_status_code(str(e)) | ||
| print(json.dumps({"statusCode": status_code, "error": str(e)})) |
There was a problem hiding this comment.
I don't want it to raise necessarily because I don't want it to prematurely abort before it reports on the results of the files
There was a problem hiding this comment.
maybe I'm confused then, should we catching a different exception? AirflowAPIError reads as if the trigger_dag_run request failed and the dag never started
Co-authored-by: Jamison French <50224594+jjfrench@users.noreply.github.com>
There was a problem hiding this comment.
Looks good, I just realized that we have one more task to handle new dataset/collection publication and it looks like the existing promote_ scripts could be generalized as publish_ scripts to support both publication and promotion.
I approve of these changes if we want to make a second PR to handle both new dataset and collection publication and promotion
|
EDIT: I see that we are already using the promote_ scripts for new dataset publication. The language is confusing but if the functionality is working I guess we are OK. Maybe eventually we can touch up the readme to clarify that in this context promote does not only mean promote from staging to prod it also just means publish. Regardless, I am glad we don't have another PR to open :) |
https://github.com/NASA-IMPACT/veda-architecture/issues/849
What Changed
scripts/airflow_api.pythat triggers that DAGs according to the version it identifies based on env var settings