-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add template_searchpath Support via Config for DAG Rendering (#53792) #54256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Nataneljpwd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Great job!
Only 1 comment that needs to be resolved and its perfect
d949b2d to
34972df
Compare
Nataneljpwd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
|
Removed hardcoded default value |
|
This needs a test. |
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
+1 |
Added unit tests to verify template_searchpath behavior with both single and multiple paths configured. |
Co-authored-by: Elad Kalif <45845474+eladkal@users.noreply.github.com>
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
|
Hi @uranusjr, I’ve updated the PR with the changes based on your feedback. Could you kindly review it again and let me know if anything else? |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
template_searchpathas a documented config option inconfig_templates/config.ymlThis was suggested in #53972 as a more scalable approach instead of adding more CLI args or making it per-DAG. This PR implements that feedback .
Closes #53972