digitalservicebund/Validate STACKIT Database ACLs
A github action that uses the STACKIT API to ensure that database ACLs only allow the cluster to connect to the database instances.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 7, 2026
- License
- MIT
Pinned Snippet
uses: digitalservicebund/stackit-database-validation@9a569f6d04b9a0ffd72afb0c6b962729e5ad2197 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| organisation_id | The Organisation ID, to validate all Databases in your STACKIT organisation. Either provide organisation_id or project_id | no | — |
| project_id | The Project ID, to validate all Databases in your STACKIT project. | no | — |
| prod_egress_range | The CIDR Range of the production cluster | no | — |
| non_prod_egress_range | The CIDR Range of the non-prod cluster | no | — |
| stackit_service_account_key | STACKIT Service Account Key to authenticate against STACKIT API | yes | — |
| additional_non_prod_ip | Additional IP address or CIDR range that should be allowed to access non-prod databases. | no | — |
| additional_prod_ip | Additional IP address or CIDR range that should be allowed to access prod databases. | no | — |
Outputs
no outputs