Problem Description: When Signing is enabled but signing service not defined in the database, the end user has no log message for diagnostics.

Proposed Solution: Add messages to the featureflags

 

{ "execution_environments":true "collection_signing":true "signatures_enabled":true, "require_upload_signatures":false, "can_create_signatures":false, "can_upload_signatures":false, "collection_auto_sign":false, "display_signatures":false, "_messages": [ "WARNING: collection_signing is enabled, however SigningService is not set on the database." ] }

Reminders:

• Set the affected Component(s): Backend, Infrastructure, Pulp, QE, Security, UI
• Apply labels "crc-automation-hub" and/or "private-automation-hub" to indicate if the issue is for Cloud Automation Hub, Private Automation Hub, or both