Enforce Kebab-Case Policy Names in Validation and API Specs

[DakshithaS]

Description

The existing policy name validation allowed uppercase letters, underscores, and other non-URL-friendly characters. This change enforces strict kebab-case naming while preserving existing length constraints, ensuring policy names are consistent, URL-friendly, and compliant with web standards.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[DakshithaS]

Validation Rules

• ✅ Must use only lowercase letters and numbers
• ✅ Hyphens allowed as separators between alphanumeric segments
• ✅ Must start and end with alphanumeric characters
• ✅ No consecutive hyphens allowed
• ✅ No uppercase letters or underscores
• ✅ Length: 3-64 characters (enforced in regex)

Valid Examples

• rate-limit
• api-key-validator
• custom-policy-v2
• traffic-control

Invalid Examples

• RateLimit (contains uppercase)
• rate_limit (contains underscore)
• -rate-limit (starts with hyphen)
• rate-limit- (ends with hyphen)
• rate--limit (consecutive hyphens)

Benefits

• URL-Friendly: No encoding needed, follows RFC 3986 standards
• SEO-Friendly: Lowercase with hyphens preferred for web URLs
• API Consistency: Uniform naming across all policy endpoints
• Human-Readable: Clear, predictable policy names in URLs