ENP Connect to ENP DB when Deployed

[EvanParish]

User Story - Business Need

Currently the deployed ENP code cannot connect to the ENP database hosted in RDS. This requires some changes to how we construct the database uri. It will no longer be passed in a single environment variable and will need to be constructed from a few different ones, see Additional Info below.

• Sync with Kyle when ticket is picked up.
• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a backend engineer
I want to connect to the database when the application is deployed
So that the FastAPI codebase is useable when deployed

Additional Info and Resources

• We will need to alter the code to build the database connection string based on the appropriate secrets. These secrets are available as environment variables.
  • DB_AUTH
  • DB_HOSTNAME
  • DB_HOSTNAME_READ

Acceptance Criteria

• When ENP is deployed the code can connect to our ENP database in RDS
• Local database connection is still intact for running the app locally
• This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

• Endpoints that rely on ENP database connections are able to execute successfully

The routes that rely on the ENP db are currently just:

• GET and POST /db/test

Potential Dependencies

Out of Scope

[cris-oddball]

Requested changes from @EvanParish and added changes requested label.

We have two databases that enp needs to connect to, the ENP DB and the Notification-API DB. The epic that is it is in implies the notification-api DB but it's not clear to me.

[cris-oddball]

Evan confirmed that this is for connecting to the ENP database.