Spacelift currently requires all policies to use the hardcoded package name “spacelift”. This request is to allow users to configure custom package names or support multiple packages per policy.
The problem description got truncated. This is the complete text:
All Spacelift policies must declare package spacelift, which forces every policy into a single shared namespace. This causes:
Symbol collisions — Rules and functions with the same name across policies conflict, forcing us to prefix duplicated code in similar policies.
Broken OPA tooling — Linting and test execution don't work well with a shared namespace. Tests cannot be scoped per package and must be run per individual policy file instead.
No shared code — It is impossible to create a separate helper package with reusable logic and import it into multiple policies.
Log in to comment and vote
Comments1
Pink Soup
Jun 5
The problem description got truncated. This is the complete text:
All Spacelift policies must declare package spacelift, which forces every policy into a single shared namespace. This causes:
Symbol collisions — Rules and functions with the same name across policies conflict, forcing us to prefix duplicated code in similar policies.
Broken OPA tooling — Linting and test execution don't work well with a shared namespace. Tests cannot be scoped per package and must be run per individual policy file instead.
No shared code — It is impossible to create a separate helper package with reusable logic and import it into multiple policies.