how are you invoking in your day to day? | Dagger | Page 1

I'm currently using task run and wrapping up the more complicated calls to dagger as it's very very low overhead. Has watch capability. Mage feels redudant when coding in dagger so task feels just right.

I could setup some aliases i suppose in envrc with direnv or such, but task provides a bit of low hanging glue.

Anyone using finding they still use a lightweight wrapper or markdown code snippet style execution for tasks or are you riding bareback with some 🤠 style dagger invocations for every call on the cli?

this gets a bit unwieldy. To be fair, I could set defaults for all this and reduce it I guess.

dagger call issues \
      -v \
      --org-id=all \
      --format=csv \
      --dedup=true \
      --days=7
      --token=env:SNYK_TOKEN \
      export --path .artifacts/

dagger call issues --token=env:SNYK_TOKEN export --path .artifacts/

The second is better, with export being required and mapping in env variable explicitly it's a bit of a mouthful to a newbie in a project still.

#how are you invoking in your day to day?