From 3224a223d483e2d7059903501ff54d313e17ac83 Mon Sep 17 00:00:00 2001
From: JM Faircloth <jmfaircloth@hashicorp.com>
Date: Wed, 31 Jul 2024 14:01:14 -0500
Subject: [PATCH] docs: add namespace example to readme

---
 README.md | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 5570c2a..55f0279 100644
--- a/README.md
+++ b/README.md
@@ -486,7 +486,6 @@ steps:
       uses: hashicorp/vault-action
       with:
         url: https://vault-enterprise.mycompany.com:8200
-        caCertificate: ${{ secrets.VAULT_CA_CERT }}
         method: token
         token: ${{ secrets.VAULT_TOKEN }}
         namespace: admin
@@ -496,6 +495,25 @@ steps:
             secret/data/ci npm_token
 ```
 
+Alternatively, you may need to authenticate to the root namespace and retrieve
+a secret from a different namespace. To do this, do not set the `namespace`
+parameter. Instead set the namespace in the secret path. For example, `<NAMESPACE>/secret/data/app`:
+
+```yaml
+steps:
+    # ...
+    - name: Import Secrets
+      uses: hashicorp/vault-action
+      with:
+        url: https://vault-enterprise.mycompany.com:8200
+        method: token
+        token: ${{ secrets.VAULT_TOKEN }}
+        secrets: |
+            namespace-1/secret/data/ci/aws accessKey | AWS_ACCESS_KEY_ID ;
+            namespace-1/secret/data/ci/aws secretKey | AWS_SECRET_ACCESS_KEY ;
+            namespace-1/secret/data/ci npm_token
+```
+
 ## Reference
 
 Here are all the inputs available through `with`: