Repurpose .venomrc into an environment-aware config file about venom HOT 2 CLOSED

We have wrapped our executions with a custom bash script that gets the environment and test that we want to trigger as arguments.

One thing that we are doing is that we consolidate all the yaml files in a directory to a single a single yaml file and we provide it to venom.

If you have your directories named after your environments then it is easy to execute venom in the right context.

script_directory is the current path that you are working on
CONTEXT_DIR is the directory you want to output the files to start a test
VARIABLES_DIR is a directory path ( ie env/dev or env/staging )

We use yq for merging all those yaml files into one ( ignoring any starting with example_... )

  
  touch "${script_directory}/${CONTEXT_DIR}/initial_variables.yml"

  files_to_merge=()
  for file in "${script_directory}/${VARIABLES_DIR}"/*.yml; do
    filename=$(basename "$file")
    if [[ "${filename}" =~ ^example_.* ]]; then
      echo "Ignoring ${filename}"
    else
      echo "appending ${file}"
      files_to_merge+=" vars/${filename}"
    fi
  done

  docker run --rm \
  --mount type=bind,source="${script_directory}/${CONTEXT_DIR}",target=/workdir/out \
  --mount type=bind,source="${script_directory}/${VARIABLES_DIR}",target=/workdir/vars \
  mikefarah/yq ea '. as $item ireduce ({}; . * $item )' ${files_to_merge}  > "${script_directory}/${CONTEXT_DIR}/initial_variables.yml"

Then in the venom execution

venom run ${test_file} --var-from-file="${script_directory}/${CONTEXT_DIR}/initial_variables.yml" --format=json --html-report 

from venom.

It's a nice idea, but I'm not sure if it's venom's responsibility to maintain a dictionary of variables. Just like handling parallelism on venom run command, I think this needs to be done outside of venom.
Thank you @fokion for the example.

from venom.