Merge pull request #6 from stakater/renovate/stakater-.github-0.x

Update stakater/.github action to v0.0.34
stakater · Apr 27, 2023 · e2d500d · e2d500d
2 parents 96eb39d + 1bbcc8c
commit e2d500d
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/.github/workflows/pull_request.yaml b/.github/workflows/pull_request.yaml
@@ -7,13 +7,13 @@ on:
 
 jobs:
   qa:
-    uses: stakater/.github/.github/workflows/pull_request_doc_qa.yaml@v0.0.29
+    uses: stakater/.github/.github/workflows/pull_request_doc_qa.yaml@v0.0.34
     with:
       MD_CONFIG: .github/md_config.json
       DOC_SRC: content
       MD_LINT_CONFIG: .markdownlint.yaml
   build:
-    uses: stakater/.github/.github/workflows/pull_request_container_build.yaml@v0.0.29
+    uses: stakater/.github/.github/workflows/pull_request_container_build.yaml@v0.0.34
     with:
       DOCKER_FILE_PATH: Dockerfile
     secrets:

diff --git a/.github/workflows/push.yaml b/.github/workflows/push.yaml
@@ -7,7 +7,7 @@ on:
 
 jobs:
   push:
-    uses: stakater/.github/.github/workflows/push_container.yaml@v0.0.29
+    uses: stakater/.github/.github/workflows/push_container.yaml@v0.0.34
     with:
       DOCKER_FILE_PATH: Dockerfile
       RELEASE_BRANCH: main

diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
@@ -7,6 +7,6 @@ on:
 
 jobs:
   release:
-    uses: stakater/.github/.github/workflows/release_template.yaml@v0.0.29
+    uses: stakater/.github/.github/workflows/release_template.yaml@v0.0.34
     secrets:
       SLACK_WEBHOOK_URL: ${{ secrets.STAKATER_DELIVERY_SLACK_WEBHOOK }}
diff --git a/content/external-secret-operator/workflow.md b/content/external-secret-operator/workflow.md
@@ -16,7 +16,7 @@ Secret Store `tenant-vault-secret-store` is already created in each namespace by
 
 ### Step 3
 
-Service account `tenant-vault-access` being referred by `SecretStore` is already created by Multi Tenant Operator templates. This service account has the `stakater.com/vault-access: 'true'` label, which is used to bound it with the Vault `role` by Multi Tenant Operator. To learn how Multi Tenant Operator authenticates with Vault, see [Vault Multitenancy](https://docs.stakater.com/mto/vault-multitenancy.html).
+Service account `tenant-vault-access` being referred by `SecretStore` is already created by Multi Tenant Operator templates. This service account has the `stakater.com/vault-access: 'true'` label, which is used to bound it with the Vault `role` by Multi Tenant Operator. To learn how Multi Tenant Operator authenticates with Vault, see [Vault Multitenancy](https://docs.stakater.com/mto/main/vault-multitenancy.html).
 
 ### Step 4
 

diff --git a/content/managed-service/offer.md b/content/managed-service/offer.md
@@ -31,7 +31,7 @@ Vault's audit logs and metrics will be available. Logs will be written to a sepa
 
 ## Namespace multi-tenancy
 
-[Stakater Multi Tenant Operator](https://docs.stakater.com/mto/index.html) not only provides strong multi-tenancy, but also automatically manages RBAC for tenant secrets through tenant paths and policies.
+[Stakater Multi Tenant Operator](https://docs.stakater.com/mto/main/index.html) not only provides strong multi-tenancy, but also automatically manages RBAC for tenant secrets through tenant paths and policies.
 
 ## Kubernetes integration