Support files on service, stage and project level to be mapped into job container

[grabnerandi]

Right now the list of files specified in the job/config.yaml instruct the job-executor-service to download those files & directories from the service for the current stage. A great capability of some of the keptn services such as jmeter, helm, dynatrace ... is that they also fetch files from service and project level. This allows a user to provide "stage global" or "project global" files that can be re-used by each service.

I would like to propose that capability for the Job Executor as well where referenced files are looked up on project, stage and service level, See it like an "inheritence" option for files. If a file is only present in project or stage I get it from there. If a file is availalbe on multiple layers I get the one "closest to service".

Example for locust
project/locust/locust.py
stage-dev/locust/locust.conf.yaml
stage-dev/locust/locust-file2.py
stage-dev/my-service/locust/locust.conf.yaml

If I know execute a task in the context of stage-dev and my-service I would get the following files

• /locust/locust.py (from project scope)
• /locust/locust-file2.py (from stage scope)
• /locust/locust.conf.yaml (from service scope as this one has higher priority then the file on stage scope)