default schedule name when none provided
ClosedPublic
Actions

Authored by • sandyryza on Jul 12 2021, 4:56 PM.

Details

Reviewers

alangenfeld
• cdecarolis

Commits

R1:55cc0b990214: default schedule name when none provided

Summary

job name + "_schedule"

Test Plan

Diff Detail

Repository

R1 dagster

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

• sandyryza created this revision.Jul 12 2021, 4:56 PM

• sandyryza added a child revision: D8824: crag migration guide.Jul 12 2021, 5:00 PM

Harbormaster returned this revision to the author for changes because remote builds failed.Jul 12 2021, 5:18 PM

Harbormaster failed remote builds in B33557: Diff 41420!

Harbormaster returned this revision to the author for changes because remote builds failed.Jul 12 2021, 6:22 PM

Harbormaster failed remote builds in B33564: Diff 41431!

Test failure is unrelated

absolute-win

This revision is now accepted and ready to land.Jul 12 2021, 8:43 PM

Harbormaster completed remote builds in B33581: Diff 41456.Jul 12 2021, 9:50 PM

Closed by commit R1:55cc0b990214: default schedule name when none provided (authored by • sandyryza). · Explain WhyJul 12 2021, 10:00 PM

This revision was automatically updated to reflect the committed changes.

• sandyryza added a commit: R1:55cc0b990214: default schedule name when none provided.

Revision Contents
Changeset List

Path

Size

python_modules/

dagster/

core/

definitions/

schedule.py

22 lines

dagster_tests/

core_tests/

definitions_tests/

test_schedule.py

24 lines

Diff 41476

View Options

python_modules/dagster/dagster/core/definitions/schedule.py