Update stakater/.github action to v0.0.122 (0.11)

.github/workflows/closed_pr.yaml

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

.github/workflows/delete_branch.yaml

@@ -5,7 +5,7 @@ on:
 
 jobs:
   delete:
-    uses: stakater/.github/.github/workflows/[email protected].117
+    uses: stakater/.github/.github/workflows/[email protected].122
     with:
       LATEST_DOC_VERSION: "1.1"
     secrets:

.github/workflows/pull_request.yaml

@@ -8,19 +8,19 @@ on:
 
 jobs:
   doc_qa:
-    uses: stakater/.github/.github/workflows/[email protected].117
+    uses: stakater/.github/.github/workflows/[email protected].122
     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].117
+    uses: stakater/.github/.github/workflows/[email protected].122
     secrets:
       GH_TOKEN: ${{ secrets.PUBLISH_TOKEN }}
   build_container:
     needs: deploy_doc
     if: ${{ github.base_ref == 'main' }}
-    uses: stakater/.github/.github/workflows/[email protected].117
+    uses: stakater/.github/.github/workflows/[email protected].122
     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].117
+    uses: stakater/.github/.github/workflows/[email protected].122
     with:
       LATEST_DOC_VERSION: "1.1"
     secrets:

.github/workflows/release.yaml

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

Dockerfile

@@ -18,4 +18,4 @@ LABEL name="Multi Tenant Operator Documentation" \
 
 EXPOSE 8080:8080/tcp
 
-CMD ["nginx", "-g", "daemon off;"]
+CMD ["nginx", "-g", "daemon off;"]

content/changelog.md

@@ -420,7 +420,7 @@
 ### v0.2.32
 
 - refactor: Restructure integration config spec, more details in [relevant docs][def]
-- feat: Allow users to input custom regex in certain fields inside of integration config, more details in [relevant docs](./how-to-guides/integration-config.md#openshift)
+- feat: Allow users to input custom regex in certain fields inside of integration config, more details in [relevant docs](./how-to-guides/integration-config.md)
 
 ### v0.2.31
 

content/faq.md

@@ -8,7 +8,7 @@
 unable to find annotation openshift.io/sa.scc.uid-range
 ```
 
-**Answer.** OpenShift recently updated its process of handling SCC, and it's now managed by annotations like `openshift.io/sa.scc.uid-range` on the namespaces. Absence  of them wont let pods schedule. The fix for the above error is to make sure ServiceAccount `system:serviceaccount:openshift-infra.` regex is always mentioned in `Privileged.serviceAccounts` section of `IntegrationConfig`. This regex will allow operations from all `ServiceAccounts` present in `openshift-infra` namespace. More info at [Privileged Service Accounts](./how-to-guides/integration-config.md#privileged-serviceaccounts)
+**Answer.** OpenShift recently updated its process of handling SCC, and it's now managed by annotations like `openshift.io/sa.scc.uid-range` on the namespaces. Absence  of them wont let pods schedule. The fix for the above error is to make sure ServiceAccount `system:serviceaccount:openshift-infra.` regex is always mentioned in `Privileged.serviceAccounts` section of `IntegrationConfig`. This regex will allow operations from all `ServiceAccounts` present in `openshift-infra` namespace. More info at [Privileged Service Accounts](./how-to-guides/integration-config.md)
 
 ## Namespace Admission Webhook
 

content/tutorials/vault/enabling-multi-tenancy-vault.md

@@ -22,7 +22,7 @@ This requires a running `RHSSO(RedHat Single Sign On)` instance integrated with
 
 MTO integration with Vault and RHSSO provides a way for users to log in to Vault where they only have access to relevant tenant paths.
 
-Once both integrations are set up with [IntegrationConfig CR](../../how-to-guides/integration-config.md#rhsso-red-hat-single-sign-on), MTO links tenant users to specific client roles named after their tenant under Vault client in RHSSO.
+Once both integrations are set up with [IntegrationConfig CR](../../how-to-guides/integration-config.md), MTO links tenant users to specific client roles named after their tenant under Vault client in RHSSO.
 
 After that, MTO creates specific policies in Vault for its tenant users.
 

prepare_theme.sh

@@ -1,3 +1,3 @@
 pip install -r theme_common/requirements.txt
-python theme_common/scripts/combine_theme_resources.py theme_common/resources theme_override/resources dist/_theme
+python theme_common/scripts/combine_theme_resources.py -s theme_common/resources -ov theme_override/resources -o dist/_theme
 python theme_common/scripts/combine_mkdocs_config_yaml.py theme_common/mkdocs.yml theme_override/mkdocs.yml mkdocs.yml

theme_override/mkdocs.yml

@@ -3,6 +3,18 @@ docs_dir: content
 site_url: https://docs.stakater.com/mto/
 repo_url: https://github.com/stakater/mto-docs
 edit_uri: blob/main/content/
+theme:
+  favicon: assets/images/favicon.svg
+
+strict: true
+validation:
+  links:
+    anchors: warn
+
+extra:
+  version:
+    provider: mike
+    default: latest
 
 nav:
     - index.md