feat: new deployment provider - F5 Big-IP

[ckyvra]

Description

Add support for F5 Big-IP as a deployment provider for Certimate.

F5 Big-IP is a load-balancing appliance widely used in enterprise environments. This provider will automatically upload and deploy SSL certificates via the iControl REST API.

Two modes are proposed:

• certificate: upload only (certificate + private key)
• clientssl: upload + assign to an existing client-ssl profile

The provider should:

• Auto-generate a stable F5 object name from the certificate SAN (e.g. certimate_example_com)
• Support wildcard certificates (*. prefix stripped from the name)
• Allow configuration of the target partition (default: Common)
• Support username/password authentication with optional insecure connection toggle

Motivation

Currently, deploying a certificate issued by Certimate to F5 is a manual process (export, upload via UI, assign to profile). A native F5 deployment provider would:

1. Close the loop: issue → deploy becomes a single workflow
2. Reduce human error in certificate deployment
3. Enable automated certificate renewal with zero-touch F5 deployment
4. Support enterprise compliance requirements for certificate lifecycle automation

F5 holds a significant share of the ADC/load-balancer market, and adding this provider addresses a recurring request from enterprise users.

Miscellaneous

Reference implementation: PR #1349 already has a working implementation with:

• Go SDK client for the iControl REST API (pkg/sdk3rd/f5bigip/)
• Provider implementation with both upload and clientssl modes
• Unit tests
• UI credential and deployment forms
• English and Chinese i18n

Contribution

• I am interested in contributing a PR for this!

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Feature Request

Add support for F5 Big-IP as a deployment provider for Certimate.

Description

F5 Big-IP is a load-balancing appliance. The provider will automatically import SSL certificates via the iControl REST API, with the possibility of assigning the certificate to an existing client-ssl profile.

Proposed implementation

• Provider type: f5bigip
• Two modes: upload only (certificate) or upload + client-ssl update (clientssl)
• Auth: username/password
• PR: feat(provider): new deployment provider: F5 Big-IP #1349

[fudiwei]

certimate/.github/ISSUE_TEMPLATE/2-feature_request.yml

Line 15 in edfe07b

4. Please describe the problem in detail according to the template specification, otherwise the issue will be closed directly.

It's disappointing you didn't use the correct issue template, as it makes both the AI-generated code and this issue look questionable.

Just to clarify: I'm not against AI-assisted coding (I use it too). However, the key is to follow the guidelines and fully understand the changes being made.

At this point, your contributions resemble those of an automated script creating random PRs. I’m left wondering if there is a genuine developer overseeing this process.

[ckyvra]

Thank you for these encouraging remarks. I'll do what's necessary to meet the standards. I haven't developed good habits yet. For the other PRs, I'll take care of them soon to get them in order. Also on certmate which you also maintain. In any case, incredible work on your side for these two solutions that very well cover the automatic renewal problems we're going to encounter.