Using ${td.last_results.job_count} causes an error with --dry-run about digdag HOT 4 CLOSED

it's because td.last_results.job_count is not available when you don't run the workflow. --dry-run doesn't run the workflow.

from digdag.

I think what we can is that digdag run -d reads status file from digdag.status.
If status file is there, use it.
Otherwise, show a warning like "this task didn't run before. following tasks might see warnings about lack of parameters"...

from digdag.

This is difficult to solve by the current design of dry-run. Because parameters are run-time information, dry-run can't evaluate all parameters. Therefore, what it can is just showing order of execution and templates without evaluation. This is not dry-run, but a sort of visualizations.

So, digdag will remove dry-run, and add another subcommand that shows execution order and parameters (without total evaluation) visually.

from digdag.

Close the old issue. Please reopen or file new one if you need.

from digdag.