yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-10-06 22:35:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(docs): correct role name in azure key vault documentation (#21024)

Browse Source
This commit is contained in:
wadhah mahrouk 2025-04-29 19:55:48 +02:00 committed by GitHub
parent 7b223abdbd
commit d3a607198d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
openmetadata-docs/content/v1.6.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md
View File

@ -46,7 +46,7 @@ While the Airflow part only needs to read the secrets hence the role `Key Vault
1. In your Key Vault overview page, note down the `Vault URI`.
2. Go to `Access Control (IAM)` and click on `Add Role Assignment`.
3. Give the permission `Key Vault Secrets Users` to your Principal.
3. Give the permission `Key Vault Secrets User` to your Principal.
### 3. Update configuration

2
openmetadata-docs/content/v1.7.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md
View File

@ -46,7 +46,7 @@ While the Airflow part only needs to read the secrets hence the role `Key Vault
1. In your Key Vault overview page, note down the `Vault URI`.
2. Go to `Access Control (IAM)` and click on `Add Role Assignment`.
3. Give the permission `Key Vault Secrets Users` to your Principal.
3. Give the permission `Key Vault Secrets User` to your Principal.
### 3. Update configuration

2
openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md
View File

@ -46,7 +46,7 @@ While the Airflow part only needs to read the secrets hence the role `Key Vault
1. In your Key Vault overview page, note down the `Vault URI`.
2. Go to `Access Control (IAM)` and click on `Add Role Assignment`.
3. Give the permission `Key Vault Secrets Users` to your Principal.
3. Give the permission `Key Vault Secrets User` to your Principal.
### 3. Update configuration