chore(deps): update stakater/.github action to v0.0.112 (main) (#232)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Karl Johan Grahn <[email protected]>

.github/workflows/closed_pr.yaml

@@ -7,6 +7,6 @@ on:
 
 jobs:
   push:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     secrets:
       GH_TOKEN: ${{ secrets.PUBLISH_TOKEN }}

.github/workflows/delete_branch.yaml

@@ -4,7 +4,7 @@ on: delete
 
 jobs:
   delete:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     with:
       LATEST_DOC_VERSION: "1.0"
     secrets:

.github/workflows/pull_request.yaml

@@ -8,19 +8,19 @@ on:
 
 jobs:
   doc_qa:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     with:
       MD_CONFIG: .github/md_config.json
       DOC_SRC: content README.md
       MD_LINT_CONFIG: .markdownlint.yaml
   deploy_doc:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     secrets:
       GH_TOKEN: ${{ secrets.PUBLISH_TOKEN }}
   build_container:
     needs: deploy_doc
     if: ${{ github.base_ref == 'main' }}
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     with:
       DOCKER_BUILD_CONTEXTS: content=https://github.com/stakater/mto-docs.git#pull-request-deployments
       DOCKER_FILE_PATH: Dockerfile

.github/workflows/push.yaml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   push:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     with:
       LATEST_DOC_VERSION: "1.0"
     secrets:

.github/workflows/release.yaml

@@ -7,11 +7,11 @@ on:
 
 jobs:
   create_release:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     secrets:
       SLACK_WEBHOOK_URL: ${{ secrets.STAKATER_DELIVERY_SLACK_WEBHOOK }}
   build_container:
-    uses: stakater/.github/.github/workflows/[email protected].110
+    uses: stakater/.github/.github/workflows/[email protected].112
     with:
       DOCKER_BUILD_CONTEXTS: content=https://github.com/stakater/mto-docs.git#gh-pages
       DOCKER_FILE_PATH: Dockerfile

content/about/key-features.md

@@ -92,7 +92,7 @@ More details on [Sandboxes](../tutorials/tenant/create-sandbox.md)
 
 Multi Tenant Operator supports cloning of secrets and configmaps from one namespace to another namespace based on label selectors. It uses templates to enable users to provide reference to secrets and configmaps. It uses a template group instance to distribute those secrets and namespaces in matching namespaces, even if namespaces belong to different tenants. If template instance is used then the resources will only be mapped if namespaces belong to same tenant.
 
-More details on [Copying Secrets and ConfigMaps](../tutorials/distributing-resources/copying-resources.md)
+More details on [Copying Secrets and Configmaps](../tutorials/distributing-resources/copying-resources.md)
 
 ### Self-Service
 

content/crds-api-reference/integration-config.md

@@ -502,7 +502,7 @@ argocd:
 
 ### Vault
 
-[Vault](https://www.vaultproject.io/) is used to secure, store and tightly control access to tokens, passwords, certificates, encryption keys for protecting secrets and other sensitive data using a UI, CLI, or HTTP API.
+[Vault](https://www.vaultproject.io/) is used to secure, store and tightly control access to tokens, passwords, certificates, encryption keys for protecting secrets and other sensitive data using a UI, CLI, or http API.
 
 If `vault` is configured on a cluster, then Vault configuration can be enabled.
 

content/how-to-guides/deploying-private-helm-charts.md

@@ -53,7 +53,7 @@ Multi Tenant Operator will pick up the credentials from the mentioned namespace
 
 Afterward, Bill can see that manifests in the chart have been successfully created in all label matching namespaces.
 
-## Deploying Helm Chart to Namespaces via TemplateGroupInstances from HTTPS Registry
+## Deploying Helm Chart to Namespaces via TemplateGroupInstances from `HTTPS` Registry
 
 Bill, the cluster admin, wants to deploy a helm chart from `HTTPS` registry in namespaces where certain labels exists.
 

content/how-to-guides/distributing-secrets-using-sealed-secret-template.md

@@ -71,7 +71,7 @@ spec:
 
 Bill has added support for a new label `distribute-image-pull-secret: true"` for tenant projects/namespaces, now MTO will add that label depending on the used field.
 
-Finally, Bill creates a `TemplateGroupInstance` which will deploy the sealed secrets using the newly created project label and template.
+Finally, Bill creates a `TemplateGroupInstance` which will deploy the Sealed Secrets using the newly created project label and template:
 
 ```yaml
 apiVersion: tenantoperator.stakater.com/v1alpha1
@@ -86,4 +86,4 @@ spec:
   sync: true
 ```
 
-MTO will now deploy the sealed secrets mentioned in `Template` to namespaces which have the mentioned label. The rest of the work to deploy secret from a sealed secret has to be done by Sealed Secrets Controller.
+MTO will now deploy the Sealed Secrets mentioned in `Template` to namespaces which have the mentioned label. The rest of the work to deploy secret from a Sealed Secret has to be done by Sealed Secrets Controller.

content/how-to-guides/enabling-multi-tenancy-vault.md

@@ -1,6 +1,6 @@
 # Configuring Vault in IntegrationConfig
 
-[Vault](https://www.vaultproject.io/) is used to secure, store and tightly control access to tokens, passwords, certificates, and encryption keys for protecting secrets and other sensitive data using a UI, CLI, or HTTP API.
+[Vault](https://www.vaultproject.io/) is used to secure, store and tightly control access to tokens, passwords, certificates, and encryption keys for protecting secrets and other sensitive data using a UI, CLI, or http API.
 
 To enable Vault multi-tenancy, a role has to be created in Vault under [Kubernetes authentication](https://developer.hashicorp.com/vault/docs/auth/kubernetes) with the following permissions:
 

content/how-to-guides/integrating-vault.md

@@ -5,7 +5,7 @@ This guide provides step-by-step instructions for integrating **Vault** with **K
 ## Prerequisites
 
 - Microsoft Entra ID configured for OIDC.
-- Keycloak setup with an Identity Provider (IdP) pointing to Microsoft Entra ID.
+- Keycloak setup with an Identity Provider (IDP) pointing to Microsoft Entra ID.
 - HashiCorp Vault installed and configured.
 - [Vault Configured in IntegrationConfig](enabling-multi-tenancy-vault.md)
 
@@ -32,7 +32,7 @@ This guide provides step-by-step instructions for integrating **Vault** with **K
     - Claim: groups
     - Sync Mode: FORCE
 
-   ![Keycloak IdP Mapper showing how the group IDs claim is mapped to the user attribute.](../images/keycloak-idp-mapper.png)
+   ![Keycloak IDP Mapper showing how the group IDs claim is mapped to the user attribute.](../images/keycloak-idp-mapper.png)
 
 ### Step 3: Set Up a Mapper for Vault Client in Keycloak
 

content/troubleshooting.md

@@ -43,7 +43,7 @@ If the user needs to be added immediately and it is not feasible to wait for nex
 
 ## Pod Creation Error
 
-### Q. Errors in ReplicaSet Events about pods not being able to schedule on OpenShift because scc annotation is not found
+### Q. Errors in ReplicaSet Events about pods not being able to schedule on OpenShift because SCC annotation is not found
 
 ```terminal
 unable to find annotation openshift.io/sa.scc.uid-range