A few important notes:
1. Adding the flow run ID (as shown in the example:
{{ deployment_name }}-{{ flow_run_id }}
) is recommended to ensure unique job names for each run
2. Make sure the name follows Kubernetes naming conventions (lowercase alphanumeric characters, '-' and '.')
3. The template variables are automatically populated by Prefect when the job is created
Would you like me to provide more details about other template variables you can use or about other aspects of the base job template configuration?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.