From d3a607198d2bbe1d79931e59d78ec23554a1b1e8 Mon Sep 17 00:00:00 2001 From: wadhah mahrouk <33103894+wadhah101@users.noreply.github.com> Date: Tue, 29 Apr 2025 19:55:48 +0200 Subject: [PATCH] fix(docs): correct role name in azure key vault documentation (#21024) --- .../supported-implementations/azure-key-vault/index.md | 2 +- .../supported-implementations/azure-key-vault/index.md | 2 +- .../supported-implementations/azure-key-vault/index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/openmetadata-docs/content/v1.6.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md b/openmetadata-docs/content/v1.6.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md index e1264ff8c50..ca1609f4fd6 100644 --- a/openmetadata-docs/content/v1.6.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md +++ b/openmetadata-docs/content/v1.6.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md @@ -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 diff --git a/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md b/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md index e1264ff8c50..ca1609f4fd6 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md +++ b/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md @@ -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 diff --git a/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md b/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md index e1264ff8c50..ca1609f4fd6 100644 --- a/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md +++ b/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/secrets-manager/supported-implementations/azure-key-vault/index.md @@ -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