taskotron / libtaskotron

#56 fix secret_key check in production configuration of resultsdb_frontend
Closed: Fixed Opened by tflink.

Closed: Fixed
Reopen Issue

The check to make sure Flask's secret_key isn't the default for production config is being done before any configuration is loaded and thus, always fails. This is preventing deployment of resultsdb_frontend in a production environment and needs to be fixed.

I've written a patch to fix the issue:
{F1456}

This ticket is a duplicate of https://pagure.io/taskotron/resultsdb/issue/3

I think this is completed as a part of #113.
Metadata
None
None
None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.