Currently sometimes we collect events for a specific date, however not all the events that are required to trigger a workflow are emitted. Suspect this is due to pod instability, and possibly events upstream not being re-emitted. Continuing to try to resolve the upstream issues in ticket https://github.com/bcgov/nr-rfc-grib-copy/issues/16
As a result the database can grow in size with stale events associated with days past.
This ticket would create an end point that would allow us to purge the data in the database for specified dates.
Any past date can be purged
Block any requests to purge the data associated with the current date.
Add OIDC authentication to the api - Could be complicated! May want to put that into its own ticket.
Ideally any write operations should require the user be authenticated.
Currently sometimes we collect events for a specific date, however not all the events that are required to trigger a workflow are emitted. Suspect this is due to pod instability, and possibly events upstream not being re-emitted. Continuing to try to resolve the upstream issues in ticket https://github.com/bcgov/nr-rfc-grib-copy/issues/16
As a result the database can grow in size with stale events associated with days past.
This ticket would create an end point that would allow us to purge the data in the database for specified dates.