Skip to content

DM-54505: Implement Scheduled Campaigns#246

Draft
tcjennings wants to merge 10 commits intomainfrom
tickets/DM-54505/schedule
Draft

DM-54505: Implement Scheduled Campaigns#246
tcjennings wants to merge 10 commits intomainfrom
tickets/DM-54505/schedule

Conversation

@tcjennings
Copy link
Copy Markdown
Collaborator

  • Implement scheduled campaigns and associated template rendering

@tcjennings tcjennings force-pushed the tickets/DM-54505/schedule branch from 126c48f to 67b5f40 Compare April 3, 2026 16:43
Base automatically changed from u/tobyj/w_2026_09 to main April 6, 2026 17:12
@tcjennings tcjennings force-pushed the tickets/DM-54505/schedule branch 3 times, most recently from 032b926 to 8368aa9 Compare April 7, 2026 20:25
- update database migration for schedules
- update tests with daemon context fixture
- update mypy config for apscheduler
- fix incidental type errors
- refresh lock file
- update jsonschema script
- remove static jsonschema
- name uq constraint in schedules table model
- improve test fixture usage
- Add model validators to Campaign, Node, Edge, and Manifest
- Use default namespace UUID from enums module
- Update some field descriptions
- refactor template rendering function to produce ORM objects
- implement schedule job trigger function
@tcjennings tcjennings force-pushed the tickets/DM-54505/schedule branch from 8368aa9 to 3d5c202 Compare April 7, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant