When using the new jinja templating in ObjectStorage, it seems that it's misinterpreting the protocol of the string and prepending a forward slash "/" to my GCS bucket name.
Perhaps it's evaluating the protocol before rendering the jinja string.
What you think should happen instead?
When using jinja templating for variable in ObjectStorage, I'm getting the following:
/gs:/redox-n-airflow-workspace-us-central1
rather than the correct variable name:
gs://redox-n-airflow-workspace-us-central1
EDIT:
I tested the theory that it's interpreting the protocol before rendering and I suspect that's the case given the output below. It wasn't the output I expected because it added google_cloud_default@ I'm guessing based on this str
Open to it, but have never contributed. The jinja templating is a bit magical to me and if it's happening in the wrong order, I'm unsure it's an easy enough fix for someone of my skill level.
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Apache Airflow version
2.10.1
If "Other Airflow 2 version" selected, which one?
No response
What happened?
When using the new jinja templating in ObjectStorage, it seems that it's misinterpreting the protocol of the string and prepending a forward slash "/" to my GCS bucket name. Perhaps it's evaluating the protocol before rendering the jinja string.
What you think should happen instead?
When using jinja templating for variable in ObjectStorage, I'm getting the following: /gs:/redox-n-airflow-workspace-us-central1
rather than the correct variable name: gs://redox-n-airflow-workspace-us-central1
How to reproduce
Logging prints the following:
EDIT: I tested the theory that it's interpreting the protocol before rendering and I suspect that's the case given the output below. It wasn't the output I expected because it added
google_cloud_default@
I'm guessing based on this strOperating System
linux amd64
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct