feat: add initial version from internal repository

.config/.pre-commit-config.yaml

@@ -0,0 +1,21 @@
+---
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.1.0
+    hooks:
+      - id: fix-byte-order-marker
+      - id: check-added-large-files
+        args:
+          - "--maxkb=20"
+      - id: check-case-conflict
+      - id: check-yaml
+      - id: check-json
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: mixed-line-ending
+      - id: check-merge-conflict
+      - id: check-shebang-scripts-are-executable
+  - repo: https://github.com/pre-commit/mirrors-prettier
+    rev: v2.6.0
+    hooks:
+      - id: prettier

.config/cspell.json

@@ -0,0 +1,54 @@
+{
+  "version": "0.2",
+  "language": "en",
+  "words": [
+    "aesgcm",
+    "ciphertext",
+    "cpus",
+    "dockerhub",
+    "Hapag",
+    "Infracost",
+    "oidc",
+    "pytest",
+    "Repology",
+    "tflint",
+    "tfsec",
+    "virtualenv"
+  ],
+  "ignoreWords": [
+    "AKIA",
+    "amannn",
+    "aquasecurity",
+    "automerge",
+    "automerged",
+    "boto",
+    "buildcache",
+    "buildx",
+    "codeowners",
+    "codeql",
+    "conventionalcommits",
+    "datasource",
+    "dorny",
+    "hadolint",
+    "hlag",
+    "hmarr",
+    "ibiqlik",
+    "kayman",
+    "ludeeus",
+    "markdownlint",
+    "maxsplit",
+    "mktemp",
+    "ossrh",
+    "pascalfrenz",
+    "rhysd",
+    "ruleset",
+    "sarif",
+    "shellcheck",
+    "shuf",
+    "shunsuke",
+    "signoff",
+    "stty",
+    "venv",
+    "vuln"
+  ]
+}

.config/markdownlint.yml

@@ -0,0 +1,12 @@
+---
+# Default state for all rules
+default: true
+
+# MD013/line-length - Line length
+MD013:
+  # Number of characters
+  line_length: 132
+  # Number of characters for headings
+  heading_line_length: 132
+  # Number of characters for code blocks
+  code_block_line_length: 132

.config/yamllint.yml

@@ -0,0 +1,8 @@
+---
+extends: default
+
+rules:
+  line-length:
+    max: 132
+  comments:
+    min-spaces-from-content: 1 # Renovate uses 1 space only

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# maintainers of the project
+*   @kayman-mk @PascalFrenz

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+see CODEOWNERS.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/CONTRIBUTING.md

@@ -0,0 +1,25 @@
+# Contribution guide
+
+We appreciate your thought to contribute to open source. :heart: We want to make contributing as easy as possible. You are welcome to:
+
+- Report a bug
+- Discuss the current state of the code
+- Submit a fix
+- Propose new features
+
+We use [Github Flow](https://guides.github.com/introduction/flow/index.html), so all code changes happen through pull
+requests. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `main`.
+2. If you've added code, check one of the examples.
+3. Make sure your code lints.
+4. Raise a pull request.
+
+## Documentation
+
+We use [pre-commit](https://pre-commit.com/) for some default checks which are fast and find the most common errors.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the license available at
+[LICENSE](blob/main/LICENSE).

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Found a bug? Report it!
+title: ''
+labels: new, bug
+assignees: ''
+---
+
+<!-- Before submitting a bug, make sure that you meet the following requirements:
+  1. use the latest version of the module
+  2. read the documentation
+-->
+
+# Describe the bug
+
+A clear and concise description of what the bug is.
+
+# To Reproduce
+
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+# Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+# Additional context
+
+Add any other context about the

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,39 @@
+---
+name: Feature Request
+about: Propose a new feature
+title: ''
+labels: new, enhancement
+assignees: ''
+---
+
+# Describe the solution you'd like
+
+<!--
+  Provide a clear and concise description of what you want to happen. Add some sentences to describe the use case
+  to be solved by this feature.
+-->
+
+# Describe alternatives you've considered
+
+<!--
+  Let us know about other solutions you've tried or researched.
+-->
+
+# Suggest a solution
+
+<!--
+Things to include:
+
+- details of the technical implementation
+- tradeoffs made in design decisions
+ -caveats and considerations for the future
+
+If there are multiple solutions, please present each one separately. Save comparisons for the very end.
+-->
+
+# Additional context
+
+<!--
+  Is there anything else you can add about the proposal?
+  You might want to link to related issues here, if you haven't already.
+-->

.github/pull_request_template.md

@@ -0,0 +1,23 @@
+# Description
+
+What is the overall goal of your PR? Which problem does it solve? Please also include relevant motivation and context.
+List any dependencies that are required for this change.
+
+Fixes #(issue number)
+
+# Migrations required
+
+yes: please describe the migration
+no: please delete the whole paragraph
+
+# Verification
+
+This paragraph is usually not needed if automated tests are in place for the change.
+
+Please describe the test cases you used to verify your code. Did you check the change in your environment?
+
+# Checklist
+
+- [ ] My code follows the style guidelines of the project
+- [ ] I have performed a self-review of my own code
+- [ ] I have made corresponding changes to the documentation

.github/renovate.json5

@@ -0,0 +1,5 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+
+  "extends": ["github>Hapag-Lloyd/Renovate-Global-Configuration"]
+}

.github/workflows/linter.yml

@@ -0,0 +1,11 @@
+---
+name: Lint files
+
+# yamllint disable-line rule:truthy
+on:
+  pull_request:
+
+jobs:
+  default:
+    uses: Hapag-Lloyd/Repository-Templates/.github/workflows/default_linter_callable.yml@13628b3a168ca0096a52ecf93fa1a92295580a9f
+    secrets: inherit

.github/workflows/pull_request.yml

@@ -0,0 +1,18 @@
+---
+name: "Pull Request"
+
+# yamllint disable-line rule:truthy
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+    branches-ignore:
+      - "release-please--branches--*"
+
+jobs:
+  default:
+    # yamllint disable-line rule:line-length
+    uses: Hapag-Lloyd/Repository-Templates/.github/workflows/default_pull_request_callable.yml@13628b3a168ca0096a52ecf93fa1a92295580a9f
+    secrets: inherit