This message was deleted.

Hi! 1. This is currently unsupported. I forgot to document this so thanks for your feedback. we'll add it! 2. If your environment is called `something`You can create an

env.something.yaml

file. Soopervisor will pick that up and use it instead of the

env.yaml

by default. Let me know if this solves your issue!

Thank you for the answers! Out of curiosity, do you have any intention of adding support to dag-level hooks in the future? About the params, I meant something more like this:

apiVersion: <http://argoproj.io/v1alpha1|argoproj.io/v1alpha1>
kind: Workflow
metadata:
  generateName: project-name-
spec:
  entrypoint: dag
  arguments:
    parameters:
    - name: param1
      value: value1
    - name: param2
      value: value2
  templates:
  - inputs:
      parameters:
      - name: task_name
    name: run-task
    script:
      command:
      - bash
      image: image-name
      source: |-
        ploomber task {{inputs.parameters.task_name}} --entry-point pipeline.yaml --force \
        --env--param1 {{workflow.parameters.param1}} --env--param2 {{workflow.parameters.param2}}
      volumeMounts: []
      workingDir: null
  - dag:
    ...

basically being able to override parameters from the workflow.

Re dag-level hooks: it's now on our radar (we prioritize things that users bring up, so thanks!); but I can't promise a date. we're a small team 😅 Re env: maybe there's something I'm missing here but you can achieve the same result with the solution I suggested

env.yaml

contains your environment default values

env.argo.yaml

contains the values you can use in Argo (you can use

import from

to get the values from

env.yaml

so this second file only has the values you need to override, see here) then, if your soopervisor environment is called

argo

, then soopervisor will use

env.argo.yaml

as the environment, achieving the same effect as if you did

--env--param

inside the YAML. Does this work?

Re hooks: got it! Thank you for your effort! Re env: I guess the use case is a little different, if I'm not missing something. With the

env.argo.yaml

I can specify parameters for any environment, but those parameters are also bundled within the generated image. The use case I'm facing is instead generating more of a "template" - I have a pipeline which has some default parameters, but I can choose to run the workflow with new parameters without re-running soopervisor. (That is, if I have understood correctly how env files work)

ah I got it now. So the problem is that the parameters as bundled with the image but you want to use the same image with different parameters. it's not supported currently interesting, this is something I didn't think before. I'll open an issue so we keep track of it!

Thank you!