Summary

Adds support for embedding custom Rego rules when consuming Poutine as a library or extending it as a CLI. This allows projects like pkg-supply and spicy-poutine to bundle their own rules alongside Poutine's built-in rules in a single self-contained binary without filesystem dependencies.

Problem

Library consumers and CLI extensions who want to add custom Rego rules currently must:

• Write embedded rules to temporary files at runtime
• Manage filesystem paths and cleanup
• Deal with potential permission issues and deployment complexity

This prevents truly self-contained binary deployments.

Solution

For Library Consumers

New constructor in opa/opa.go:

//go:embed rules
var CustomRules embed.FS

opa, err := poutineOpa.NewOpaWithEmbeddedRules(ctx, config, CustomRules)

For CLI Extensions

New exported variable in cmd/root.go:

//go:embed rules
var CustomRules embed.FS

func main() {
    poutineCmd.CustomEmbeddedRules = &CustomRules
    poutineCmd.Execute()
}

All commands (built-in and custom) automatically use the embedded rules.

Changes

opa/opa.go:

• Added NewOpaWithEmbeddedRules() constructor for library usage
• Modified Compile() to load custom embedded rules alongside built-in rules
• Custom rules respect skip and allowed rule filters

cmd/root.go:

• Added CustomEmbeddedRules exported variable
• Updated newOpa() and newOpaWithConfig() to use embedded rules when set

Tests:

• TestNewOpaWithEmbeddedRules - verifies custom rules load and execute
• TestEmbeddedRulesWithSkipAndAllowed - confirms rule filtering works

Backward Compatibility

✅ Fully backward compatible - existing usage works unchanged

🤖 Generated with Claude Code