CMS - Lighthouse: push Vet Center CAP data

[kevwalsh]

ACs

• [ ] CAP data as defined here https://github.com/department-of-veterans-affairs/va.gov-cms/issues/4410
• [ ] Add automated test to existing queueing mechanism to make sure cap is pushed or not.
• [ ] Send Lighthouse an actual payload through slack to they build to it.
• [ ] Do not push CAPs without lat/lon (it is required by Lighthouse)
• [ ] CAP data is only pushed when its node is published. (will have to work out a status that can be pushed when a CAP is archived.)
• [ ] Any fields pushed to Lighthouse have a corresponding content model document that indicates it is being pushed.
• [ ] Send data by a push to their sandbox?? and confirm with Lighthouse that data is received. (this may need to be a separate issue, as there will be dev time on their side.)

This AC is still up in the air:

• [ ] Shutting down a CAP? I expect the lighthouse team confirms the endpoint approach with the facilities dev working on this card add, update and delete endpoint? OR one endpoint? OR something else

[omahane]

Do we currently push facility data when the node hasn't been published (e.g., vet_center, vet_center_outstation)?

[swirtSJW]

Do we currently push facility data when the node hasn't been published (e.g., vet_center, vet_center_outstation)?

We push facility statuses when a node is not published so that the Facility API has the current status even if there is no FE page published. The difference with CAPs is that they originate in the CMS. They do not exist in the Facility API until they are published in the CMS and we push them to FAPI. CAPs have a chicken and Egg problem that none of the other facility types have.

[kmariepat-cityfriends]

There is a PR that has the CAP data ready to push, waiting on LH to make an endpoint and potentially they may come back with changes

[jilladams]

Most recent PR: https://github.com/department-of-veterans-affairs/va.gov-cms/pull/16837