Add Hasura Events Views

[Mythicaeda]

• Tickets addressed: Closes Show error if mission model upload fails #1273 (backend portion)
• Review: By commit
• Merge strategy: Merge (no squash)

Description

Creates a SQL function to get the event logs for a specified Hasura event, and three views that select from this function, one for each of our Hasura events.

While the views could not be necessary had I actually created and tracked a custom table for the function return type in order to satisfy the Hasura Custom Function API (as is done with our other Hasura functions), by using views we can establish relationships between the results and the mission_model table, allowing for queries like so:

query {
  mission_model{
    id
    refresh_activity_type_logs { success }
    refresh_resource_type_logs { success }
    refresh_model_parameter_logs { success }
  }
}

Note that using a function for the view definitions is required, as the Hasura tables the views reference do not exist during database initialization (Hasura creates and manages them). View definitions must be executable at the time of creation, but functions do not have this restriction.

This PR also fixes some minor bugs in our Migrations pipeline. Specifically:

• Fixed the PGCMP Workflow. Checking out develop requires re-cloning the PGCMP repo. The workflow was doing this pre-2.8.0, but I accidentally removed it when updating it for 2.8.0.
• Fixed a bug in the migration script that was causing hasura to reapply migration 1 when bulk migrating down from version 1. This bug was introduced in 2.8.0.
• Fixed a typo in the migration script preventing the "mark correct version" command from applying. The hasura command is case-sensitive. This bug was introduced in 2.8.0.

Verification

Manual verification was done to figure out the schema for errors and to check the Hasura metadata.

An E2E test was added to the MissionModelTests suite for testing the ability to get these logs. Additionally, the model upload process now awaits these logs, replacing the Thread.sleep in HasuraFunctions.uploadMissionModel

While checking if any tests were delaying for these events to complete, I noticed that SchedulingTests.BeforeEach was inconsistent in how it uploaded the model compared to other tests classes (it caught and rethrew the potential InterruptedException as a RuntimeException). This has been resolved.

Documentation

Docs ticket here: NASA-AMMOS/aerie-docs#147

Future work

A front-end ticket is needed to track displaying success/failures for model uploads.

[skovati]

Looks good to me! Excited to have our first migration in the new DB!

[skovati]

Forgot to ask in my review, where is the migration script "typo" that you fixed? Just the "aerie" vs "Aerie"?

[Mythicaeda]

Just the "aerie" vs "Aerie"?

Yeah, apparently Hasura's case sensitive 🥲