DM-48445: Replace ScriptTemplates with Jinja Template #160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes ScriptTemplates from the application.
Does not deprecate or remove APIs related to ScriptTemplates, but eliminates the use of ScriptTemplates from both seed (example) files and script-generation functions and methods.
The concept of "script templates" is refactored using Jinja template files with "snippets" enabled or disabled based on configuration flags, e.g., "wms: htcondor" enables a template block that switches on the value of
wms
. In this way, a single template file can be considered, updated, and rendered according to the specific needs of a campaign instead of pulling in multiple template snippets from the database.This pattern is also used in the process of writing a bash script to submit to htcondor for execution, with a simplified approach to setting up a "condor" or a "panda" stack environment and without the extra steps concerning clobbering and reimplementing environment variables in the shebang.