Adding `transaction_id` Support in SSL Storage API

[iprouteget]

Hello!

I wanted to first reach out here to see if it is feasible to add support for the transaction_id parameter within the SSL storage API endpoints. Particularly, I'm working with CreateStorageSSLCertificate, ReplaceStorageSSLCertificate, and DeleteStorageSSLCertificate.

I'm thinking the general workflow would handle the following actions in a single transaction:

• Add a new certificate to storage
• Update (replace) an existing certificate in storage
• Delete an existing certificate in storage
• Add/Remove/Update crt_store and crt_load (which already support transaction_id)

The goal would be to reload HAProxy only once after doing the above actions. Tying all of these to a single transaction_id would be super handy to manage from an operational standpoint.

If this is too much overhead or is not feasible at the moment, all good. We can get away with skip_reload when adding/updating/removing certificates from storage now that #365 was merged/closed.

Thank you for your time!

[mjuraga]

Hi, currently we don't support transactions in our storage endpoints unfortunately, and this is something we definitely are looking at, and it's on our roadmap. Depending on other priorities this will be added in one of the future versions.