Apply fixes

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -6,7 +6,7 @@ body:
   # information
   - type: markdown
     attributes:
-      value: | 
+      value: |
         Thanks for taking the time to fill out this bug report!
         *Note:* Please search to see if an issue already exists for the bug you encountered.
   # bug description
@@ -27,10 +27,10 @@ body:
       placeholder: Tell us what steps you did to encounter the bug!
       render: bash
       value: |
-        1. 
-        2. 
-        3. 
-        4. 
+        1.
+        2.
+        3.
+        4.
     validations:
       required: true
   # expected behavior
@@ -47,7 +47,7 @@ body:
     id: additional-context
     attributes:
       label: Additional context
-      description: | 
+      description: |
         Add any other context about the problem here.
         If applicable, you can add screenshots to help explain your problem.
       placeholder: Anything that might help us understanding your problem...
@@ -62,7 +62,7 @@ body:
     attributes:
       label: Version (kapitan)
       description: |
-        Which version of kapitan are you running? 
+        Which version of kapitan are you running?
         If you are using an older version of kapitan, please try it against the master branch or the latest stable version.
       options:
         - v0.31.0 (stable)
@@ -76,11 +76,11 @@ body:
     attributes:
       label: Version (kapitan)
       description: |
-        Which version of python are you using? Kapitan officially supports only version 3.10 and 3.11 
+        Which version of python are you using? Kapitan officially supports only version 3.10 and 3.11
         If you are using an older version of python, please check if the bug still exists with a newer (supported) version.
       options:
         - "3.11"
-        - "3.10" 
+        - "3.10"
         - I use kapitan directly (pip, docker)
       multiple: true
     validations:
@@ -107,7 +107,7 @@ body:
     id: logs
     attributes:
       label: Relevant log output
-      description: | 
+      description: |
         Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
         Use the `--verbose` flag to see all the logs.
       render: bash

.github/ISSUE_TEMPLATE/config.yml

@@ -7,4 +7,4 @@ contact_links:
 - name: '💬 Join us on Slack'
   url: https://kubernetes.slack.com/archives/C981W2HD3
   about: |
-    Join our Slack channel to connect with our community, ask questions, and stay updated on project developments.
+    Join our Slack channel to connect with our community, ask questions, and stay updated on project developments.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -6,15 +6,15 @@ body:
   # information
   - type: markdown
     attributes:
-      value: | 
+      value: |
         Thanks for taking the time to give us feedback!
   # feature description
   - type: textarea
     id: documentation-issue-description
     attributes:
       label: Description of the documentation issue
       description: |
-        A clear and concise description of what the issue with documentation is. 
+        A clear and concise description of what the issue with documentation is.
         Please make proposals, how it could be done better.
       placeholder: Tell us what you want to see in the project!
     validations:
@@ -24,6 +24,6 @@ body:
     id: additional-context
     attributes:
       label: Additional context
-      description: | 
+      description: |
         Add any other context about the feature here.
       placeholder: Anything that might help us understanding your documentation issue...

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -6,15 +6,15 @@ body:
   # information
   - type: markdown
     attributes:
-      value: | 
+      value: |
         Thanks for taking the time to fill out this feature request!
   # feature description
   - type: textarea
     id: feature-description
     attributes:
       label: Description of the feature
       description: |
-        A clear and concise description of what the feature request is. 
+        A clear and concise description of what the feature request is.
         Please make proposals, how you would use this feature (syntax).
       placeholder: Tell us what you want to see in the project!
     validations:
@@ -24,6 +24,6 @@ body:
     id: additional-context
     attributes:
       label: Additional context
-      description: | 
+      description: |
         Add any other context about the feature here.
       placeholder: Anything that might help us understanding your feature request...

.github/dependabot.yml

@@ -24,4 +24,4 @@ updates:
     schedule:
       interval: "daily"
     labels:
-      - "github-actions"
+      - "github-actions"

.github/pull_request_template.md

@@ -7,4 +7,4 @@ Fixes #
 ## Docs and Tests
 
 * [ ] Tests added
-* [ ] Updated documentation
+* [ ] Updated documentation

.github/workflows/documentation.yml

@@ -12,7 +12,7 @@ on:
       - 'docs/**'
       - '.github/workflows/documentation.yml'
       - 'mkdocs.yml'
-      - 'CNAME' 
+      - 'CNAME'
   push:
     branches:
       - master

.github/workflows/housekeeping.yml

@@ -11,9 +11,9 @@ jobs:
         with:
           stale-issue-message: |
             This issue is stale because it has been open for 1 year with no activity.
-            Remove the stale label or comment if this issue is still relevant for you. 
+            Remove the stale label or comment if this issue is still relevant for you.
             If not, please close it yourself.
           days-before-issue-stale: 365
           day-before-pr-stale: -1
           days-before-close: -1
-          days-before-pr-close: -1
+          days-before-pr-close: -1

.github/workflows/pex-build-upload.yml

@@ -15,7 +15,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Install poetry
-        run: |- 
+        run: |-
           pipx install poetry
           pipx inject poetry poetry-plugin-export --force
       - name: Set up Python
@@ -47,7 +47,7 @@ jobs:
             --python=python3.12 \
             -m kapitan \
             -o dist/kapitan.linux-x86_64.pex
-          dist/kapitan.linux-x86_64.pex --help 
+          dist/kapitan.linux-x86_64.pex --help
 
       - name: Add linux-x86_64 pex to assets
         uses: softprops/action-gh-release@v2

.github/workflows/python-pip-publish.yml

@@ -4,7 +4,7 @@ name: Upload Python Package
 concurrency:
   group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
   cancel-in-progress: true
-  
+
 on:
   workflow_dispatch:
   release:

.github/workflows/test-build-publish.yml

@@ -6,7 +6,7 @@ concurrency:
   group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
   cancel-in-progress: true
 
-on: 
+on:
   push:
     branches:
       - master
@@ -37,7 +37,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
       - uses: psf/black@main
-  
+
   test:
     name: python ${{ matrix.python-version }} tests
     runs-on: ubuntu-latest
@@ -60,7 +60,7 @@ jobs:
           python-version: ${{ matrix.python-version }}
       - name: Install libraries dependencies
         run: |
-          poetry install --no-root 
+          poetry install --no-root
       - name: Install testing dependencies (Helm)
         run: |
           sudo apt-get -qq update
@@ -92,7 +92,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           submodules: recursive
-      
+
       # Setup QEMU and Buildx to build multi-platform image
       # This was inspired by this example : https://docs.docker.com/build/ci/github-actions/examples/#multi-platform-images
       - name: Set up QEMU
@@ -104,7 +104,7 @@ jobs:
       - name: build Kapitan Image
         uses: docker/build-push-action@v6
         with:
-          push: False 
+          push: False
           platforms: ${{ matrix.platform }}
           load: True
           file: Dockerfile
@@ -134,7 +134,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           submodules: recursive
-      
+
       # Setup QEMU and Buildx to build multi-platform image
       # This was inspired by this example : https://docs.docker.com/build/ci/github-actions/examples/#multi-platform-images
       - name: Set up QEMU
@@ -223,7 +223,7 @@ jobs:
             type=semver,pattern={{version}}
             type=semver,pattern={{major}}.{{minor}}
             type=semver,pattern={{major}}
-            
+
       - uses: int128/docker-manifest-create-action@v1
         env:
           DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME}}
@@ -233,4 +233,4 @@ jobs:
           builder: buildx
           suffixes: |
             -linux-amd64
-            -linux-arm64
+            -linux-arm64

.markdownlintignore

@@ -1,4 +1,4 @@
 examples/
 tests/
 kapitan/
-PULL_REQUEST_TEMPLATE.md
+PULL_REQUEST_TEMPLATE.md

.pre-commit-config.yaml

@@ -7,4 +7,12 @@ repos:
     rev: 5.13.2
     hooks:
       - id: isort
-        args: [--profile, black]
+        args: [--profile, black]
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: check-docstring-first
+      - id: debug-statements
+      - id: end-of-file-fixer
+      - id: check-merge-conflict

CNAME

@@ -1 +1 @@
-kapitan.dev
+kapitan.dev

_config.yml

@@ -1 +1 @@
-markdown: kramdown
+markdown: kramdown

compiled/minikube-es/script.sh

@@ -4,4 +4,4 @@ set -ex
 
 compile_dir=$1
 
-echo "This is going into a file" > "${compile_dir}/${FILE_NAME}"
+echo "This is going into a file" > "${compile_dir}/${FILE_NAME}"

docs/ADOPTERS.md

@@ -17,4 +17,4 @@ If you're using **Kapitan** in your organization, please let us know by adding t
 -   [![Ubisoft](adopters_logos/ubisoft.png){: style="height:100px"}](https://www.ubisoft.com/)
 -   [![VSHN AG](adopters_logos/vhsn.png){: style="height:100px"}](https://www.vshn.ch)
 -   [![Flower Labs](adopters_logos/flower.png){: style="height:100px"}](https://www.flower.ai)
-</div>
+</div>

docs/CNAME

@@ -1 +1 @@
-kapitan.dev
+kapitan.dev

docs/README.md

@@ -3,7 +3,7 @@
 ![GitHub Sponsors](https://img.shields.io/github/sponsors/kapicorp?style=for-the-badge)
 ![GitHub Stars](https://img.shields.io/github/stars/kapicorp/kapitan?style=for-the-badge)
 
-**Kapitan** aims to be your *one-stop configuration management solution* to help you manage the ever growing complexity of your configurations by enabling **Platform Engineering** and **GitOps** workflows. 
+**Kapitan** aims to be your *one-stop configuration management solution* to help you manage the ever growing complexity of your configurations by enabling **Platform Engineering** and **GitOps** workflows.
 
 It streamlines complex deployments across heterogeneous environments while providing a secure and adaptable framework for managing infrastructure configurations.  **Kapitan**'s inventory-driven model, powerful templating capabilities, and native secret management tools offer granular control, fostering consistency, reducing errors, and safeguarding sensitive data.
 
@@ -12,7 +12,7 @@ Empower your team to make changes to your infrastructure whilst maintaining full
 * :fontawesome-brands-slack: Join the community [`#kapitan`](https://kubernetes.slack.com/archives/C981W2HD3)
 * :fontawesome-brands-github: Help us grow: [give us a star](https://github.com/kapicorp/kapitan/stargazers) or even better [sponsor our project](pages/contribute/sponsor/)
 
-## [Why do I need **Kapitan**?](pages/blog/posts/2022-12-04.md#why-do-i-need-kapitan) 
+## [Why do I need **Kapitan**?](pages/blog/posts/2022-12-04.md#why-do-i-need-kapitan)
 
 ## [Video Tutorials to get started](https://www.youtube.com/@kapitandev)
 
@@ -28,4 +28,4 @@ Empower your team to make changes to your infrastructure whilst maintaining full
         <iframe width="1024" height="576" src="https://www.youtube.com/embed/clPkDuC2bY4?si=GQwMGNpXuucUTwri" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
 
     === "Rawkode: Introduction to Kapitan"
-        <iframe width="1024" height="576" src="https://www.youtube.com/embed/8QZvgJi0vII?si=iqLZXv9VvoJD4hTT" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+        <iframe width="1024" height="576" src="https://www.youtube.com/embed/8QZvgJi0vII?si=iqLZXv9VvoJD4hTT" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

docs/getting_started.md

@@ -1,6 +1,6 @@
 # :kapitan-logo: **Kapitan Overview**
 
-## Setup your installation 
+## Setup your installation
 
 Using our reference repositories you can easily get started with **Kapitan**
 
@@ -94,7 +94,7 @@ Compiled echo-server (0.14s)
         kapitan -h
         ```
 
-### Pip 
+### Pip
 
 #### Install Python
 

docs/kap_proposals/kap_11_hashicorp_vault_transit.md

@@ -66,7 +66,7 @@ parameters:
         VAULT_SKIP_VERIFY: "True"
         auth: token
         mount: transit
-        crypto_key: new_key   
+        crypto_key: new_key
         always_latest: False
 ```
 
@@ -76,7 +76,7 @@ Extra parameters that can be defined in inventory are:
 * `auth`: specify which authentication method to use like `token`,`userpass`,`ldap`,`github` & `approle`
 * `mount`: specify the mount point of key's path. e.g if path=`alpha-secret/foo/bar` then `mount: alpha-secret` (default `secret`)
 * `crypto_key`: Name of the `encryption key` defined in vault
-* `always_latest`: Always rewrap ciphertext to latest rotated `crypto_key` version  
+* `always_latest`: Always rewrap ciphertext to latest rotated `crypto_key` version
 Environment variables __should NOT__ be defined in inventory are `VAULT_TOKEN`,`VAULT_USERNAME`,`VAULT_PASSWORD`,`VAULT_ROLE_ID`,`VAULT_SECRET_ID`.
 This makes the secret_inside_kapitan file accessible throughout the inventory, where we can use the secret whenever necessary like `?{vaulttransit:${target_name}/secret_inside_kapitan}`
 

docs/kap_proposals/kap_1_external_dependencies.md

@@ -14,10 +14,10 @@ parameters:
   dependencies:
    - type: git | http[s]
      output_path: <output_path>
-     source: <git/http[s]_url>    
+     source: <git/http[s]_url>
 ```
 
-The output path is the path to save the dependency into. For example, it could be `/components/external/manifest.jsonnet`. Then, the user can specify the fetched file as a `kapitan.compile` item along with the locally-created files.  
+The output path is the path to save the dependency into. For example, it could be `/components/external/manifest.jsonnet`. Then, the user can specify the fetched file as a `kapitan.compile` item along with the locally-created files.
 
 Git type may also include `ref` and `subdir` parameters as illustrated below: