Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Consider supporting .jinja2 extensions across the project
See original GitHub issueDescription
At the moment, various operators support reading templates from given filenames (for example, bash_command of BashOperator). However, all of these operators specify extensions such as .sh, .json etc., so it means users need to write Jinja2 templates inside .sh, .json files. A better way to do it would be supporting the .jinja2 extension.
Use case / motivation
The motivation is threefold:
.jinja2extension is a widespread convention which is supported by various editors, including Github itself, PyCharm and VSCode.- Putting templates inside
.jinja2can help distinguish between regular files and template files just by looking at the directory contents - Working with tools that recognize
.jinja2templates can help reduce errors while authoring templates.
Related Issues
https://github.com/apache/airflow/pull/8572#discussion_r416473395
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No, actually this is a bit different i.e. the OP wants to allow using “file.jinja2” instead of “file.bash” or “file.sql” in rendered template fields.
@kaxil this issue should be resolved by https://github.com/apache/airflow/pull/14603 correct?