eManifest go-live checklists

[cmc333333]

WIP

Before

• Ideally: come up with better strategy than dropping whole db
• Commit ethnio code (should be parameterized)
• Update cloud.gov CUPS to use regs.gov prod info (REGS_GOV_API_KEY, REGS_GOV_API_LOOKUP_URL, REGS_GOV_API_URL)
• Review Revenue Recapture equation to make sure it matches Bill's description
• Push latest data update
• Make sure DOCUMENT_ID (currently in the dev manifest file) can be set via a CUPS as well

FR published PDF & Metadata

• Update DOCUMENT_ID in cups
• Turn on ethnio (through their UI)
• Update xml meta data eregs-version-id, eregs-primary-docket, PRTPAGE, eregs-fr-volume, eregs-published-date, eregs-comments-close-on-date
• Update xml submission id: eregs-comment-doc-id
• Update xml content: grep for [insert
• Drop local db, reparse XML, check it in the UI, DELETE previous proposal. Look for a header with the FR citation, links to add comments, no longer using 0000-0000
• Drop demo db. write_to to demo, DELETE previous proposal. Restage worker, then web. Check again
• Drop live db. write_to to prod, DELETE previous proposal
• Restage worker, then web. Validate
• Launch day static content updates (eManifest static urls #37)

FR published full XML

• Parse new XML locally, review it in the UI
• Compare new content to demo's content.
• Inspect images. We may need to modify the XML if FR's don't work
• write_to prod.
• Restage web. Validate

Later

• Review what we got wrong when guessing at the XML. Notably interested in the underlined content and the nested bullets see Review differences between guessed XML and proposal #43, Can EPA proposal tweaks be automated #44

[cmc333333]

Relevant PRs all merged