professional-service-best-practices/professional-service
19
0
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions
No description
53 commits 15 branches 0 tags 2.8 MiB
Find a file
Exact
Mauritz_Uphoff c7e1ddca4f
All checks were successful
Default CI / Check for Open TODOs (push) Successful in 41s
Details
Mirror to Public GitHub / Sync Repository (push) Successful in 41s
Details
Default CI / Secret Scanner (TruffleHog) (push) Successful in 1m8s
Details
Default CI / Pre-Commit Hooks (push) Successful in 2m20s
Details
Merge pull request 'ci: add step to resolve todos' (#19) from ci/todo-pipeline into main 
Reviewed-on: #19
2026-05-12 08:28:07 +00:00
.github ci: add step to resolve todos 2026-05-12 10:24:33 +02:00
examples example(nested-folder): add warning to readme 2026-05-06 14:09:15 +02:00
modules/test-machine chore(test-machine module): add validation for variables 2026-05-05 10:13:41 +02:00
scripts chore: use proper example usernames 2026-04-16 15:32:37 +02:00
.gitignore chore(example): add example for gpus on ske cluster 2026-04-16 13:26:25 +02:00
.pre-commit-config.yaml chore: add examples and modules 2026-04-15 09:43:08 +02:00
CONTRIBUTING.md chore(docs): add hint to pre-commit to contributions doc 2026-04-16 08:38:31 +02:00
GOVERNANCE.md chore: rename project 2026-05-05 09:22:14 +02:00
LICENSE.md Initial commit 2026-04-14 11:33:55 +02:00
README.md chore: readme typo 2026-05-05 10:06:46 +02:00

README.md

STACKIT Professional Service

Welcome to the central repository for STACKIT examples, scripts, and boilerplate code!

⚠️ REPOSITORY MIRROR NOTICE

This GitHub repository is a mirror. The primary, internal source of truth for this codebase lives at: https://professional-service.git.onstackit.cloud/professional-service-best-practices/professional-service

We automatically sync changes from our STACKIT managed GIT instance to this public GitHub repository.

Want to contribute? > If you are an external contributor or do not have access to our internal systems, you are more than welcome to open Pull Requests directly here on GitHub! We will review them and merge them upstream.

The Philosophy

Let's be upfront about how this repository is maintained:

  • Strictly Best Effort: Everything you find in this repository is provided on a "best effort" basis.
  • No Guarantees on Freshness: We try our best to keep the examples, Terraform modules, and scripts up to date with the latest provider releases and API changes. However, we cannot guarantee it. Things move fast in the cloud, and some examples might become outdated over time.
  • Review Before Deploying: Do not blindly copy-paste code from here directly into a production environment.

Contents

  • examples/ — Example solutions across a variety of STACKIT products.
  • scripts/ — Helper scripts for working with STACKIT services.
  • modules/ — Ready-made Terraform modules to simplify your deployments.

How to Use This Repository

Please treat this repository as a developer playground and a resource library to get working examples.

Whenever you are starting a new project, looking for a specific implementation, or need inspiration, check here first. It is highly likely you will find a working foundation that saves you hours of reading documentation.

When using our examples, please remember to:

  1. Understand it: Read through the code and understand what resources it spins up.
  2. Adapt it: Treat the code as a starting point. You will need to tweak configurations, variables, and security guardrails to fit your specific customer environment.
  3. Test it: Always run and validate the code in a sandbox or development environment first.

Contributions Welcome

Did you find a script that is broken because of a recent update? Did you build a new, awesome example that could help your colleagues?

Since this is a best-effort repository, we highly encourage you to open a Pull Request and share your fixes or additions! We all benefit from a growing, shared knowledge base. Please refer to our CONTRIBUTING.md for guidelines on how to format your code before submitting. Because this repository is maintained on a best-effort basis, discussions and reviews may take some time. However, we strive to respond within 7 business days.