OC-911: ARI ingest dry runs

[finlay-jisc]

The purpose of this PR was to add a dry run feature to the ARI integration. In order to test the ARI integration, and to avoid the risk of the ingest timing out if a high number of ARIs need to be updated/created, a dry run feature is needed to check how the ingest will behave before each run.

---

Acceptance Criteria:

• The endpoint to run the ingest operation on int or prod now contains a dry run parameter
  • Enabling this option will cause the ingest to run without actually making any changes, including:
    • No new ARIs are created, nor any updates to existing ARIs
    • No updates to the log of previous ingests that was created as part of OC-910
    • The email (see OC-888) is still returned upon completion of the operation, including stats for what would’ve been created

---

Checklist:

• Local manual testing conducted
• Automated tests added
• Documentation updated

---

Tests:

E2E

API

---

Screenshots:

Note that the double space before "results" was fixed in a later commit after these screenshots were taken.

Dry run email (HTML/text):

Subsequent real run email (HTML/text):

This is what would be output in the email if the dry run was run without any ARIs having been imported previously (we are aware the topics are not recognised):

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
octopus	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 27, 2024 9:24am