what actually goes on under the hood when you provide an
image
job variable?
if you go into advanced tab of your Base Job Template on your work pool (regardless of which kind it is) you'll see all these
variables
like
{{ image }}
or
{{ cpu }}
that by default, will get rendered as the default on that work pool (whatever you have hardcoded as
image
in the work pool, or just prefecthq/prefect:3-latest if you haven't changed anything)
but if you override
image
by providing it as a job variable on a deployment or flow run, you're selectively overwriting that piece of config from the work pool, but only for that deployment (not other users of the work pool)
there's more docs on this here
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.