should be possible to disable a scheduled workflow

[danielnorberg]

Currently the only way to disable a scheduled workflow (so that it doesn't get run) is to push another revision to the same repo.

[frsyuki]

How do you want to declare that a schedule is disabled? Why don't you use commenting out? Or do you want to disable a schedule temporarily?

[frsyuki]

Do you mean that deleting repository is not supported? Then please update the title.

[danielnorberg]

I mean something that allows a user to disable/stop a pushed/scheduled workflow from executing without having to modify and push a new revision.

E.g. something like

# Disable the workflow
digdag disable <repo> <+name>

# ... Until
digdag enable <repo> <+name>

One of the useful scenarios for this is when a user (either the original author or another person in the same organization) doesn't actually have access to the workflow yaml file.

To make a parallell with e.g. travis-ci/circle-ci, it's possible to administratively stop/pause/disable the CI of a repo using the admin UI without having to make changes to .{travis,circle}.yml

[frsyuki]

OK. My idea was to add temporary-disabled-flag to a revision (like this: https://github.com/treasure-data/digdag/blob/master/digdag-core/src/main/java/io/digdag/core/database/DatabaseMigrator.java#L285 ) but adding flag to a schedule seems better.

I think this is useful also in production if an external service is in maintenance and we don't want to start workflow until it comes back.

Adding a disable flag to a workflow feels that require>: +name and call>: +name fails if +name is disabled. We need to decide...workflow or schedule.

[frsyuki]

309 added REST API to do this.

[danielnorberg]

https://github.com/treasure-data/digdag/pull/321

[frsyuki]

done