WS-2750: End all templates with newlines
Why this MR was a draft: testing on dev to ensure breaking up metadata.json templates' JSON into multiple lines does not cause errors. This has being tested for:
- (done) std_calibration: Capability Request 120467
- (done) std_cms_imaging: Capability Request 120468 (note: image ingestion failed because the product had already been ingested)
- (done) pims_split: Workflow request whose spool directory is
/lustre/aoc/cluster/pipeline/vlass_dev/spool/split/ccccedb7
.
What was done in this MR: Ending all templates with newlines, plus a couple of typo fixes and ensuring metadata.json templates' JSON is not just one line (for readability). Also, some templates needed "down-revision" template files created so the alembic script could downgrade the templates to the version currently in production. Some of the files in this commit are these "down-revision files".
Why 1 newline at the end:
- At minimum, it provides a style consistency.
- Also, it ensures that when we combine templates, the code behaves as we expect. For example, it's not [TEMPLATE 1][TEMPLATE 2] with no newline in between, but is [TEMPLATE 1]
-
[TEMPLATE 2]
- which is a better look, and avoids any errors that might come as a result of inconsistent styling.
Notes:
- The newline doesn't show in GitLab, but at the bottom of the view of file changes, it will say "/ No newline at end of file" if that is true.
- The templates were retrieved from prod except for any specific to cal + imaging, which were created in the work for this release and aren't on prod. Those template were retrieved from dev.
Edited by Daniel Lopez Sanders