1fanwang commented on issue #70953: URL: https://github.com/apache/airflow/issues/70953#issuecomment-5186700577
Verified [Derive DbtCloudGetJobRunArtifactOperator default file name after rendering](https://github.com/apache/airflow/pull/70336) on `dbt-cloud 4.9.3rc1`. Works as intended. Airflow 3.3.0, two identical virtualenvs: one with the RC providers, one with the previous stable release. Same Dag, same command, run through the real task runner. RPC is stubbed, and the stub asserts the value that actually reaches it. A `DbtCloudGetJobRunArtifactOperator` with a templated artifact path and no explicit `output_file_name`, so the default name is derived from the rendered path. ```bash # dbt-cloud 4.9.3rc1 AIRFLOW_HOME=$PWD/airflow_home \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70336_dbt_artifact \ .venv/bin/airflow dags test rc_70336_dbt_artifact # dbt-cloud 4.9.2, identical Dag AIRFLOW_HOME=$PWD/airflow_home_prev \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70336_dbt_artifact \ .venv-prev/bin/airflow dags test rc_70336_dbt_artifact ``` ``` # dbt-cloud 4.9.3rc1 [info] Writing path/to/manifest.json artifact for job run 1234 to 1234_path-to-manifest.json RC_CHECK_OK artifact name flattened from the RENDERED path state=success # dbt-cloud 4.9.2 AssertionError: expected '1234_path-to-manifest.json', got '1234_path/to/manifest.json' state=failed ``` The previous release derived the name from the un-rendered template, so the slashes survived into the file name. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
