Open eecavanna opened 1 year ago
@eecavanna let me know if this should be added to the next sprint. Thank you for adding the size label.
Hi @ssarrafan, I don't think so. I created it to document a possible oversight. If it is, indeed, an oversight, I think I'd file it under "code cleanup" (as opposed to, for example, "bug"). It isn't causing any problems for me and is a low priority to me. Putting it into a product backlog (as opposed to next sprint's sprint backlog) would make sense to me.
There are two environment variables that, in the new development environment, are being populated from the same source (which is the
POSTGRES_URI
key of thepostgres
secret).I think these two environment variables could be consolidated into a single one, as long as the usages of the removed one are updated. I think consolidating them would simplify deployment of the application.
I searched for both environment variable names using GitHub's code search, and found that they occur in the following places:
Environment variable name:
NMDC_DATABASE_URI
(search results: https://github.com/search?q=repo%3Amicrobiomedata%2Fnmdc-server%20NMDC_DATABASE_URI&type=code)https://github.com/microbiomedata/nmdc-server/blob/c6e1a3475ad5a86712d2c229580281521874ff25/.docker-env#L7
https://github.com/microbiomedata/nmdc-server/blob/c6e1a3475ad5a86712d2c229580281521874ff25/.env.example#L4
https://github.com/microbiomedata/nmdc-server/blob/c6e1a3475ad5a86712d2c229580281521874ff25/.github/workflows/server.yml#L45
Environment variable name:
POSTGRES_URI
(search results: https://github.com/search?q=repo%3Amicrobiomedata%2Fnmdc-server+POSTGRES_URI&type=code)