-
Notifications
You must be signed in to change notification settings - Fork 780
Add Akeyless Secret Store Documentation #4930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v1.17
Are you sure you want to change the base?
Conversation
fe6c9b4 to
2223a67
Compare
Signed-off-by: Kobbi Gal <[email protected]>
Signed-off-by: Kobbi Gal <[email protected]>
Signed-off-by: Kobbi Gal <[email protected]>
82a6453 to
899d0c9
Compare
|
@msfussell FYI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kgal-akl Great PR and looking forward to getting this into the release. Left a few comments
|
|
||
| ## Authentication Methods | ||
|
|
||
| We currently support the following authentication methods: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| We currently support the following authentication methods: | |
| The following authentication methods are supported: |
|
|
||
| ## Related links | ||
|
|
||
| - [Secrets building block]({{% ref secrets %}}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest a reference to Akeyless account creation
| ``` | ||
|
|
||
| {{% alert title="Failing Retrieval in Bulk" color="info" %}} | ||
| When retrieving secrets using the bulk API, all successfully-retrieved secrets will be returned and failed ones will be logged in the component log. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| When retrieving secrets using the bulk API, all successfully-retrieved secrets will be returned and failed ones will be logged in the component log. | |
| When retrieving secrets using the bulk API, all successfully-retrieved secrets are returned and failed ones are logged in the component log. |
|
|
||
| Or using the Dapr SDK. The example below retrieves all static secrets from path `/path/to/department`: | ||
|
|
||
| ```go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a "Language Tab" section around this, so it is then clear which language and other could be added in the future.
| ## Component Format | ||
|
|
||
| ```yaml | ||
| # yaml-language-server: $schema=../../component-metadata-schema.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This component format is wrong. It should be like this, yes?
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: akeyless
spec:
type: secretstores.akeyless
version: v1
metadata:
- name: gatewayUrl
```
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. Opened instead of #4910 as PR 4910 was targeted towards release v1.16.
Issue reference