Add Akeyless Doc #4910
Add Akeyless Doc #4910
Conversation
|
|
||
| ## Authentication Methods | ||
|
|
||
| We currently support the following authentication methods: |
There was a problem hiding this comment.
| We currently support the following authentication methods: | |
| Akeyless supports the following authentication methods: |
| curl http://localhost:3500/v1.0/secrets/akeyless/my-secret | ||
| ``` | ||
|
|
||
| This will return the secret value stored in Akeyless with the name `my-secret`. |
There was a problem hiding this comment.
| This will return the secret value stored in Akeyless with the name `my-secret`. | |
| This returns the secret value stored in Akeyless with the name `my-secret`. |
| To get started with Akeyless: | ||
|
|
||
| 1. Sign up for an Akeyless account at [https://www.akeyless.io](https://www.akeyless.io) | ||
| 2. Create an Access ID and configure your preferred authentication method |
There was a problem hiding this comment.
| 2. Create an Access ID and configure your preferred authentication method | |
| 2. Create an Access ID and configure your preferred authentication method. |
| The above examples use secrets as plain strings. It is recommended to use a local secret store such as [Kubernetes secret store]({{% ref kubernetes-secret-store.md %}}) or a [local file]({{% ref file-secret-store.md %}}) to bootstrap secure key storage. | ||
| {{% /alert %}} | ||
|
|
||
| ## Spec metadata fields |
There was a problem hiding this comment.
Can you move this section up after the proposed Component format section. See example here https://docs.dapr.io/reference/components-reference/supported-secret-stores/aws-secret-manager/
| ## Create the Akeyless component | ||
|
|
||
| To setup Akeyless secret store create a component of type `secretstores.akeyless`. See [this guide]({{% ref "setup-secret-store.md#apply-the-configuration" %}}) on how to create and apply a secretstore configuration. See this guide on [referencing secrets]({{% ref component-secrets.md %}}) to retrieve and use the secret with Dapr components. | ||
|
|
There was a problem hiding this comment.
Can you add a "Component format" section that covers all the potential field for the component. Then follow this with the "Spec metadata fields". The Authentication Methods section can then follow after this as examples of using the component with different auth methods. See example here https://docs.dapr.io/reference/components-reference/supported-secret-stores/aws-secret-manager/
2 participants
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Part of dapr/components-contrib#4036.
Issue reference