Added template_fields_renderers for MySQL Operator

[oyarushe]

Added template_fields_renderers for MySQL Operator, it relates to issue #11177

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[potiuk]

Nice, but we need a unit test here.

[turbaszek]

Interesting point, I don't think we have test for template_fields_renderes yet. What we probably should check is that renderers are proper values:

airflow/airflow/www/utils.py

Lines 351 to 370 in 01fb777

	return {
	'bash': lambda x: render(x, lexers.BashLexer),
	'bash_command': lambda x: render(x, lexers.BashLexer),
	'hql': lambda x: render(x, lexers.SqlLexer),
	'html': lambda x: render(x, lexers.HtmlLexer),
	'sql': lambda x: render(x, lexers.SqlLexer),
	'doc': lambda x: render(x, lexers.TextLexer),
	'doc_json': lambda x: render(x, lexers.JsonLexer),
	'doc_rst': lambda x: render(x, lexers.RstLexer),
	'doc_yaml': lambda x: render(x, lexers.YamlLexer),
	'doc_md': wrapped_markdown,
	'jinja': lambda x: render(x, lexers.DjangoLexer),
	'json': lambda x: json_render(x, lexers.JsonLexer),
	'md': wrapped_markdown,
	'powershell': lambda x: render(x, lexers.PowerShellLexer),
	'py': lambda x: render(get_python_source(x), lexers.PythonLexer),
	'python_callable': lambda x: render(get_python_source(x), lexers.PythonLexer),
	'rst': lambda x: render(x, lexers.RstLexer),
	'yaml': lambda x: render(x, lexers.YamlLexer),
	}

[potiuk]

Right. That works for me. Can we see the screenshot ?

[oyarushe]

Please, check the screenshots:

Test DAG:

Rendered Template:

[potiuk]

Screenshot and parameters rendering would be nice!

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[turbaszek]

Nice one!

[boring-cyborg]

Awesome work, congrats on your first merged pull request!