luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

Update partnerships.html.erb

Browse source
This commit is contained in:
Andy Manoske 2018-09-26 18:56:48 -07:00 committed by GitHub
parent 79f707edd2
commit d63e66a902
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 46 additions and 37 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

83
website/source/partnerships.html.erb
View file

@ -67,59 +67,68 @@ Please begin by completing Vault Integration Program webform to tell us about yo
Here are links to resources, documentation, examples and best practices to guide you through the Vault integration development and testing process:
</p>
<p><strong>General Vault plugin development:</strong></p>
<p><strong>General Vault Plugin Development:</strong></p>
<ul>
<li><a href="https://www.vaultproject.io/docs/internals/plugins.html">Plugins documentation</a></li>
<li><a href="https://www.vaultproject.io/guides/operations/plugin-backends.html">Guide to building Vault plugin backends</a></li>
<li><a href="https://github.com/hashicorp/vault">Vault's source code</a></li>
</ul>
Secrets Engines
Secrets engines documentation
Example of how to build, install, and maintain your own Vault secrets plugin
<p><strong>Secrets Engines</p></strong>
<ul>
<li><a href="https://www.vaultproject.io/docs/secrets/index.html">Secret engine documentation</a></li>
<li><a href="https://github.com/hashicorp/vault-auth-plugin-example">Sample plugin code</a></li>
</ul>
Authentication backends
Auth Methods documentation
Building a Vault secure plugin
<p><strong>Authentication Methods</strong></p>
<ul>
<li><a href="https://www.vaultproject.io/docs/auth/index.html">Auth Methods documentation</a></li>
<li><a href="https://www.hashicorp.com/blog/building-a-vault-secure-plugin">Example of how to build, install, and maintain auth method plugins plugin</a></li>
<li><a href="https://github.com/hashicorp/vault-auth-plugin-example">Sample plugin code</a></li>
Auth plugin sample code
<p><strong>Audit Devices</p></strong>
<p><a href="https://www.vaultproject.io/docs/audit/index.html">Audit devices documentation</a></p>
Audit devices
Audit devices documentation
<p><strong>HSM Integration</strong></p>
<p><a href="https://www.vaultproject.io/docs/enterprise/hsm/index.html">HSM documentation</a></p>
<p><a href="https://www.vaultproject.io/docs/configuration/seal/pkcs11.html">Configuration information</a></p>
HSM integration
HSM documentation
<p><strong>Storage Backends</strong></p>
<p><a href="https://www.vaultproject.io/docs/configuration/storage/index.html">Storage configuration documentation</a></p>
Vault Enterprise HSM Behavioral Changes
<p><strong>Community Forum</strong></p>
<p><a href="https://groups.google.com/forum/#!forum/vault-tool">Vault developer community forum</a></p>
Configuration information
<h3> 3. Develop and Test </h3>
<p>
The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the <a href="http://www.golang.org">Go programming language</a>. Use the plugin interface to develop your integration. All integrations should contain unit and acceptance testing.
</p>
Security details
Storage backend
Storage configuration documentation
Community form: Vault developer community forum
3. Develop and Test
The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. Use the plugin interface to develop your integration. All integrations should contain unit and acceptance testing.
4. Review
HashiCorp will review and certify your Vault integration. Please send the Vault logs and other relevant logs for verification at: vault-integration-dev@hashicorp.com. For Auth, Secret and Storage plugins, submit a GitHub pull request (PR) against the Vault project (https://github.com/hashicorp/vault). Where applicable, the vendor will need to provide HashiCorp with a test account.
5. Release
<h3> 4. Review </h3>
<p>
HashiCorp will review and certify your Vault integration. Please send the Vault logs and other relevant logs for verification at: <a href="vault-integration-dev@hashicorp.com">vault-integration-dev@hashicorp.com</a>. For Auth, Secret and Storage plugins, submit a GitHub pull request (PR) against the Vault project (https://github.com/hashicorp/vault). Where applicable, the vendor will need to provide HashiCorp with a test account.
</p>
<h3> 5. Release </h3>
<p>
At this stage, the Vault integration is fully developed, documented, tested and certified. Once released, HashiCorp will officially list the Vault integration.
</p>
6. Support
<h3>6. Support</h3>
<p>
Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the start. Getting the Vault integration built is just the first step in enabling users. Once this is done, on-going effort is required to maintain the integration and address any issues in a timely manner.
The expectation for vendors is to respond to all critical issues within 48 hours and all other issues within 5 business days. HashiCorp Vault has an extremely wide community of users and we encourage everyone to report issues however small, as well as help resolve them when possible.
</p>
<h2>Checklist</h2>
<p>Below is a checklist of steps that should be followed during the Vault integration development process. This reiterates the steps described above.</p>
<ul>
<p><li>Complete the <a href="https://docs.google.com/forms/d/e/1FAIpQLSfQL1uj-mL59bd2EyCPI31LT9uvVT-xKyoHAb5FKIwWwwJ1qQ/viewform">Vault Integration webform</a></li></p>
<p><li>Develop and test your Vault integration following examples, documentation and best practices</li></p>
<p><li>When the integration is completed and ready for HashiCorp review, send the Vault and other relevant logs to us for review and certification at: <a href="vault-integration-dev@hashicorp.com">vault-integration-dev@hashicorp.com</a></li></p>
<p><li>Once released, plan to support the integration with additional functionality and responding to customer issues </li></p>
</ul>
<h2>Contact Us</h2>
<p>For any questions or feedback, please contact us at: <a href="vault-integration-dev@hashicorp.com">vault-integration-dev@hashicorp.com</a></p>