Currently, the percona-release utility defaults to using http://repo.percona.com in some contexts, even though https://repo.percona.com is supported and preferred for secure environments.

To improve flexibility and security compliance, we request adding a parameter to allow users to explicitly choose whether to use HTTPS or HTTP when enabling repositories.

Feature Request:

Add a new command-line option to percona-release to specify the preferred scheme. For example:

Expected Behavior:

• When the parameter is present, all repository URLs configured by percona-release use the specified scheme.

• Default behavior remains unchanged to preserve compatibility.

Use Case:

• Many enterprise environments enforce HTTPS-only repository access.

• Avoids manual sed patching of /usr/bin/percona-release and .list files.

• Ensures consistency and security during automated provisioning or CI/CD deployments.