Hi @Bart_DE 

No — a single job.yml file can’t “look inside” a parameter like file_name and then decide to spin up a different job-cluster size on the fly.
Job-cluster definitions in Databricks Workflows (Jobs) are static. All the heavy-lifting has to be done outside the cluster specification: