Config: Granular env-based Solution for Connection Strings

[Samk13]

❤️ Thank you for your contribution!

Description

Add logic to build connection URLs from env vars if available
needed for helm charts security best practices.

This PR includes:

• Build DB URI
• Build Redis URL
• Build MQ URL

Partially closes: inveniosoftware/helm-invenio#112
Depends on: inveniosoftware/invenio-app-rdm#2918

Note

I created a test version encapsulated in a cached class. Let me know if you prefer this over simple functions, and I’ll update accordingly see link

Findings

• For the database URI, ensure that SQLALCHEMY_DATABASE_URI="" is set to an empty string to allow the granular variables to take effect.

• For the broker, I opted for the naming convention INVENIO_RABBITMQ_* instead of INVENIO_BROKER_*, as the latter conflicts with RabbitMQ's default naming variables. For more details, refer to the documentation here.

For reviewers:

I set up a testing instance to test these changes, with the .env file and docker-services modified, see: https://github.com/Samk13/invenio-dev-latest/tree/granular-env-vars-changes

• delete the lock file, setup again, and locally install invenio-app-rdm to set these variables.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.