Change to database exception handling

[mfcrocker]

What and why?

DB exception handling was a little bit of a scattershot approach when implemented because SQLAlchemy's exceptions aren't that good. This is a best attempt at refining it a bit for alerting purposes

How to test?

• Spin up an environment
• Kill postgres
• Do anything that would call Party
• Check Party logs for the exception

Jira

RAS-901

[SteveScorfield]

/deploy scorfs

[ras-rm-pr-bot]

Deploying to dev cluster with following parameters:

• namespace: scorfs

• tag: pr-410

• configBranch: main

• paramKey: ``

• paramValue: ``

[SteveScorfield]

/deploy scorfs

[ras-rm-pr-bot]

Deploying to dev cluster with following parameters:

• namespace: scorfs

• tag: pr-410

• configBranch: main

• paramKey: ``

• paramValue: ``

[SteveScorfield]

/deploy scorfs

[ras-rm-pr-bot]

Deploying to dev cluster with following parameters:

• namespace: scorfs

• tag: pr-410

• configBranch: main

• paramKey: ``

• paramValue: ``

[SteveScorfield]

Reviewed and tested. Works as expected. PR Approved.

[matthew-robinson-ons]

/deploy robinm3

[ras-rm-pr-bot]

Deploying to dev cluster with following parameters:

• namespace: robinm3

• tag: pr-410

• configBranch: main

• paramKey: ``

• paramValue: ``

[matthew-robinson-ons]

Changes look good and was able to recreate the exception. Might need to resolve the jinja2 vulnerability before merge as it failed the build in other repos.