I would really appreciate a Key Management Plugin for Hashicorp's Vault. It can be used in any cloud or on-prem environment and provides similar functionality to AWS Key Management.
Hi sysprg, you can use this Jira task for getting the Hashicorp key management plugin from MariaDB Enterprise Server added to MariaDB Community Server 10.9
Ralf Gebhardt
added a comment - Hi sysprg , you can use this Jira task for getting the Hashicorp key management plugin from MariaDB Enterprise Server added to MariaDB Community Server 10.9
Plugin for Hashicorp Vault ported from ES edition to CS edition, including fixes for the key rotation test. Latest of the ported commits here: https://github.com/MariaDB/server/commit/5602f73e5265cb6f6470f79084a676d650027e33
The rest of the work related to the finalization of buildbot for automatic testing of the plugin has been moved to a separate task MDEV-28025
Julius Goryavsky
added a comment - Plugin for Hashicorp Vault ported from ES edition to CS edition, including fixes for the key rotation test. Latest of the ported commits here: https://github.com/MariaDB/server/commit/5602f73e5265cb6f6470f79084a676d650027e33
The rest of the work related to the finalization of buildbot for automatic testing of the plugin has been moved to a separate task MDEV-28025
The plugin cannot be pushed into main because it breaks Debian packaging, see MDEV-28500.
If the packaging problem is fixed and fix is limited to debian packaging files, I have no objections against pushing it into 10.9 (bb-10.9-MDEV-19281-v5 a47e08aa2b + the Debian fix + rebase + git commit squash/cleanup as needed) and releasing with 10.9.1. The plugin won't be built for Windows in this release.
I also recommend setting the plugin maturity to Beta. It will allow the plugin to be used with the RC server and at the same time will leave time to investigate MDEV-28492 and look into Windows issues, and we will revisit the plugin maturity before 10.9 goes GA.
However, I don't strictly insist on Beta maturity.
Elena Stepanova
added a comment - The plugin cannot be pushed into main because it breaks Debian packaging, see MDEV-28500 .
If the packaging problem is fixed and fix is limited to debian packaging files, I have no objections against pushing it into 10.9 (bb-10.9- MDEV-19281 -v5 a47e08aa2b + the Debian fix + rebase + git commit squash/cleanup as needed) and releasing with 10.9.1. The plugin won't be built for Windows in this release.
I also recommend setting the plugin maturity to Beta. It will allow the plugin to be used with the RC server and at the same time will leave time to investigate MDEV-28492 and look into Windows issues, and we will revisit the plugin maturity before 10.9 goes GA.
However, I don't strictly insist on Beta maturity.
Hi sysprg, you can use this Jira task for getting the Hashicorp key management plugin from MariaDB Enterprise Server added to MariaDB Community Server 10.9