Add template fields renderers to operators #11177
Labels
area:providers
area:webserver
Webserver related Issues
contributors-workshop
Issues that are good for first-time contributor's workshop
good first issue
kind:feature
Feature Requests
Comments
|
Will it work with the backports :)? |
|
@potiuk Yes, but this feature will not be available in older version, but will not damage operators. We'll just have the attribute set in the class and never used. |
|
Cool! |
|
Hey, |
|
@avirlrma please feel free to open a PR referencing this issue. You don't have to change all operators at once 👍 |
|
@pkonarzewski which operators would you like to improve? |
|
I would also like to contribute on this one |
kaxil
pushed a commit
that referenced
this issue
Apr 2, 2021
See #11177. Mostly SQL fields and Python options. Two notable execeptions: * `WinRMOperator.command` is marked as a new renderer `powershell`. * A new `jinja` renderer is implemented. The Pygment lexer is called `DjangoLexer`, but [Pygments suggets rendering Jinja2 with it](https://pygments.org/docs/lexers/#pygments.lexers.templates.DjangoLexer). Fix #14543.
|
I would like to work on this issue. |
This was referenced Jul 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In #11061 we've added a nice feature of "template fields renderers". This allows users to define what renderer should be used for rendering template fields values in Web UI. This is super useful for rendering big dictionaries, bash commands, sql queries, yaml files.
Use case / motivation
Improve rendering of template fields in Airflow Web UI and remove the need of using pre-defined keywords.
Operators that should be updated with template filed renderers:
BashOperatorSimpleHttpOperatorPostgresOperatorMySQLOperatorand any other that we think may gain from this feature 😸
Related Issues
#11061
The text was updated successfully, but these errors were encountered: