[tcjennings]

• adds a CM Service campaign template file for ap_daytime
• CM template files can be directly consumed as campaign definition files for scheduled campaigns in CM service, or imported with the CM campaign edit tool.
• These templates are fully-hydrated and vsc-managed template files with dynamic/variable components.
• A CM Service scheduled campaign will read the raw file from a github link (with full ref and repo path); CM Service does not check out this repo or perform other git operations.

[hsinfang]

LGTM; a question about --qgraph-datastore-records.

Should we remove submit_ap_daytime.sh and other now-obsolete files too, now this is run in cm-service?

[hsinfang]

Comparing this to ap_pipe/scripts/LSSTCam/submit_ap_daytime.sh, --qgraph-datastore-record is left out. Was it intentional?
(https://rubinobs.atlassian.net/browse/DM-55426 may be relevant)

[hsinfang]

(though post_isr_image datasets have been generated... )

[tcjennings]

The legacy script uses pipetask directly for the qgraph generation, which is why that flag was needed. BPS includes --qgraph-datastore-records in its default set of arguments for pipetask.

CM has never used pipetask for qgraph generation; instead, it used bps acquire to generate the qgraph prior to pruning, so the argument is included by default.

Now CM doesn't separate the acquire/submit stage at all and uses the --prune-... argument to affect the same outcome with an ordinary bps submit, and still relies on the bps defaults to supply --qgraph-datastore-records where needed.