cds-snc / cds-snc/platform-forms-client
Heartbeat form submission for health checks
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 85
Description
Implement a form that regularly takes actions to act as a basis for the health checks to measure against after deployments.
### Acceptance criteria:
Try to get as many steps actioned as possible for the following product actions:
- [ ] Form responses are sent to Notify (Health check, check Notify API with a specific template ID or through a cloud watch metric alarm with specific filters.)
- [ ] Notify's call-back is working and the reliability queue is responding appropriately to the response code. (Health check, check the logs for responses from the call-back. Update the logs to include 200 responses.)
- [ ] Audit, responses, and form logs are being collected, saved, and archived
- [ ] Nagware is sending emails
- [ ] Check nagware emails on Tuesday when they send next
- [ ] 2FA codes are being sent
- [ ] The dead letter queue is working correctly (No way to check without bringing down the reliability queue)
- [ ] The application performance is running as expected
- [ ] Form responses are being submitted via the vault
- [ ] Forms are able to build from scratch
- [ ] Forms are being published
- [ ] Forms can be deleted
- [ ] Forms can be closed
**Health check form submissions should not be counted in Google analytics form submission counts.**
Contributor guide
Assessment
This issue has not been assessed yet.