Skip to content

feat: add feature flag Kustomize config and feature-flag-operator IAM role#597

Closed
kevwilliams wants to merge 1 commit into
mainfrom
feat/feature-flag-kustomize-config
Closed

feat: add feature flag Kustomize config and feature-flag-operator IAM role#597
kevwilliams wants to merge 1 commit into
mainfrom
feat/feature-flag-kustomize-config

Conversation

@kevwilliams
Copy link
Copy Markdown
Contributor

Summary

  • Add config/services/features/ directory mirroring the quota service structure to support feature flag management via the quota ResourceRegistration API
  • Add feature-flag-operator IAM Role granting minimum quota permissions needed to manage feature flags (read on ResourceRegistrations + AllowanceBuckets, full CRUD on ResourceGrants)
  • Add placeholder registrations/ component with inline documentation of the canonical ResourceRegistration shape for future feature flags
  • Wire features into the top-level config/services/kustomization.yaml aggregate component

Context

Closes #576

Test plan

  • kustomize build config/services/features/ produces a single Role resource with the expected permissions
  • kustomize build config/services/ includes the new Role without errors
  • Verify feature-flag-operator permissions match the spec: resourceregistrations get/list/watch, resourcegrants get/list/watch/create/update/delete, allowancebuckets get/list/watch

… role

Add config/services/features/ mirroring the quota service structure to
support feature flag management via the quota ResourceRegistration API.

Key changes:
- Add features/iam/roles/feature-flag-operator.yaml: Role granting the
  minimum quota permissions needed to manage feature flags — read access
  to ResourceRegistrations and AllowanceBuckets, full CRUD on
  ResourceGrants (the mechanism used to grant flags to organizations)
- Add features/registrations/kustomization.yaml: Placeholder component
  with an inline comment documenting the canonical ResourceRegistration
  shape future flags must follow (type=Feature, consumerType=Organization,
  claimingResources sentinel of FeatureGrant)
- Wire features into config/services/kustomization.yaml aggregate

Closes #576
@joggrbot
Copy link
Copy Markdown
Contributor

joggrbot Bot commented May 5, 2026

📝 Documentation Analysis

All docs are up to date! 🎉


✅ Latest commit analyzed: ba009b6 | Powered by Joggr

@kevwilliams kevwilliams requested a review from scotwells May 5, 2026 18:17
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kevwilliams
Copy link
Copy Markdown
Contributor Author

Closing — the IAM role is a subset of the existing quota.miloapis.com-manager role (see @scotwells's feedback), and the registrations/ directory is an empty placeholder that adds no deployable value. The Kustomize scaffold and first real ResourceRegistration will ship together in the same PR when the first feature flag is defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: add feature flag Kustomize config and feature-flag-operator IAM role

2 participants