dagu

This release introduces the ability to configure schedules on a per-profile basis and save the output of http.request actions to a file.

Example for different schedule per profile:

schedule:
  - expression: "*/20 * * * *"
    profile: prod
  - expression: "30 */2 * * *"
    profile: dev

Example for http executor with output:

steps:
  - id: download_script
    action: http.request
    with:
      method: GET
      url: https://example.com/install.sh
      output: "${context.paths.artifacts_dir}/install.sh"

  - id: run_script
    run: sh "${context.paths.artifacts_dir}/install.sh"
    depends: download_script

Added

• feat: add profile-scoped schedules (#2359) @yohamta0
• feat: add HTTP response file output (#2361) @yohamta0

Changed

• refactor: shorten dag-run storage prefixes (#2358) @yohamta0

Fixed

• fix: isolate sub-dag default working directories (#2356) @yohamta0
• fix: contain go-git ssh auth workaround (#2357) @yohamta0

Contributors

Thanks to our contributors for this release:

| Contribution | Contributor |
| --- | --- |
| bug: SSH handshake failed: key mismatch (#2354) | @l-we (report) |
| bug: multiple sub-DAGs in single workflow using the same files. No cleanup? (Dagu: 2.9.1) (#2352), feat: Action HTTP needs a FILE output mode (#2353) | @pommetjehorlepiep (report) |

Full Changelog: https://github.com/dagucloud/dagu/compare/v2.9.1...v2.10.0