Library structure about gatekeeper-library HOT 3 CLOSED

Unique names for the constraint template make it easier to copy templates around without losing context. It also allows storing more than one template per directory. I would argue that since the compiled templates are stored in a separate place from the source code (kubectl -f requirement), the developer argument may be moot.

One extra requirement I'd like to add:

Some way of bundling documentation with the constraints: "these are the parameters and here's what they do"

from gatekeeper-library.

Just to add some user feedback: As a user with admin background I'd actually prefer a build script which I tell which policies from this library I want to use and which then creates a helm chart containing a copy of those policies for me. Then I can simply add this chart as a local chart to my helm chart based k8s cluster setup tooling.

from gatekeeper-library.

This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

from gatekeeper-library.