Seeking Guidance on Contributing a Vault Database Plugin for DB2 RDS to the Community

Vault
1

Hello,
Our team has developed a Vault database plugin for managing dynamic credentials with IBM DB2 on AWS RDS. The plugin extends Vault’s database secrets engine to support DB2 RDS database.

Plugin Details:

  • Plugin is based on the vault-plugin-database-oracle structure
  • Implements standard Vault database plugin interface
  • Includes credential rotation and dynamic user management
  • Plugin is functional and tested in our environment
  • Repository structure matches HashiCorp conventions

We are interested in sharing this plugin with the open source community but want to ensure we follow best practices and proper procedures.

Specifically, we would appreciate guidance on:

  • Recommended licensing and handling of any DB2 dependencies.
  • Coding standards or security requirements we should adhere to.
  • The preferred method to publish and distribute such plugins.
  • Best practices for testing and documentation for Vault plugins.
  • Any specific documentation standards or templates we should follow.
  • Suggestions for community engagement and ongoing maintenance.

Any advice, relevant documentation, or examples from others who have contributed similar plugins would be very helpful.

Thank you in advance for your insights!

Nish G

2

Hello @nngn24 ,

If you open an issue in the Vault GitHub repository, and select Plugin Submission someone should be able to help with any open questions you have.

That repository also has a README.md that shares how to run acceptance tests.

1 Like