dszakallas commented on pull request #10481: URL: https://github.com/apache/airflow/pull/10481#issuecomment-691953749
@dimberman the command and args are dynamic, i.e. they could be different for each run, so the only way to customize this behavior from a pod template is to interpolate these parameters using a jinja template during runtime. I don't know if it is possible currently, but would cover more use cases more cleanly. E.g. a common use case not covered by this when the entrypoint relays the args to `airflow` but sets up some environment variables first, in which case only airflow's arguments should be passed to the script. If we had a two separate variables for the command (`['airflow']`) and args (`['run', 'tasks', 'abc', '...']`) interpolated into the pod template, we could support that behavior too, by using a static command in the pod spec, and using the dynamic args. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
