Strip API_BASE_URL and ApiKey -- nothing uses either #452
Labels
No labels
Kestra
bug
enhancement
someday
subtask
☁️ api
🎛️ infrastructure
🐞 sentry
📆 2025 Season
📝 pages
allpicks
📝 pages
picks
📝 pages
standings
🚀 performance
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
johnsturgeon/tgfp-web#452
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Both are leftovers from an external-trigger REST API that was never built.
API_BASE_URLDeclared, required at startup, read from 1Password, consumed by nothing. Its
production value is
https://tgfp.us/api, which is not a route the app serves.Because
Config.get_config()raisesKeyErroron the first missing variable,every environment -- production, development, and the test suite's
_seed_test_environment()-- has to supply it for the app to import at all.Related to #199.
ApiKeyA table, registered in
app/models/__init__.py, referenced by no auth codeanywhere. No route validates a token.
It is also in
rebuild_database.sh'sPRESERVElist, so the August 2026production rebuild carefully dumped and restored one row of credentials that
nothing can authenticate against, and the script's comment explains why they
matter.
What to do
Drop both, plus:
API_BASE_URLline inconfig/op.envand the 1Password items behind itapikeyfromPRESERVEinscripts/rebuild_database.sh, and the sentencein its header comment that justifies it
apikeytableIf an external trigger API is still wanted, that is a new design against the
current auth story, not these two.