sarth-akvaish opened a new pull request, #60739:
URL: https://github.com/apache/airflow/pull/60739

   This PR resolves the issue of not rendering SQL (other also like bash 
command) in the Rendered Templates tab in the specific Task.
   
   Fixes : https://github.com/apache/airflow/issues/60589
   
   ### **What is happening currently ?**
   
   Rendered Template fields are generated inside the task runner after jinja 
rendering and then sent to the API server to be stored in the RTIF table.
   
   The task runner only serialized the top-level template fields defined on the 
operator(for ex - configuration)
   Nested renderer paths (such as configuration.query.query) were not extracted 
or sent. 
   
   As a result The RTIF model and UI were functioning correctly, but the 
required data never reached them.
   
   ### **What changed made** 
   
   The task runner logic si updated to corrrectly capture rendered template 
values after rendering and senfd them to the API server.
   Becuase the UI is data driven, it immediately began displaying the correct 
rendered templates with proper title and syntax, without any changes in teh UI 
code.
   
   Image after fixing this issue 
   
   <img width="1297" height="694" alt="Screenshot from 2026-01-18 12-23-18" 
src="https://github.com/user-attachments/assets/702db139-6d4a-4eb0-a0d8-470edd9f08f0";
 />
   
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


-- 
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]

Reply via email to