Skip to content

fix(iam): include PlatformAccessRejection in CRD kustomization; drop dead Denial CRD#580

Merged
zachsmith1 merged 1 commit intomainfrom
fix/iam-kustomization-missing-crds
Apr 28, 2026
Merged

fix(iam): include PlatformAccessRejection in CRD kustomization; drop dead Denial CRD#580
zachsmith1 merged 1 commit intomainfrom
fix/iam-kustomization-missing-crds

Conversation

@zachsmith1
Copy link
Copy Markdown
Contributor

@zachsmith1 zachsmith1 commented Apr 28, 2026

Summary

Two related fixes to config/crd/bases/iam:

1. Add missing PlatformAccessRejection entry to the kustomization

PlatformAccessRejection was introduced in 41e0bec alongside PlatformAccessApproval (the commit message reads "introduce platform access approval, rejection, and invitation resources"), but the kustomization update in that commit only added the approval entry. The rejection YAML, Go type, controller, and webhook were all created in the same commit — only the kustomization line was missed.

PAR is a real, in-use type:

  • 120 Go references in milo
  • Webhook at internal/webhooks/iam/v1alpha1/platformaccessarejection_webhook.go
  • Controller wiring in userinvitation_controller.go

2. Delete dead PlatformAccessDenial CRD manifest + regenerated docs

iam.miloapis.com_platformaccessdenials.yaml exists in the directory but PlatformAccessDenial has zero references anywhere else in the milo codebase — no Go type, no controller, no webhook. It was an orphaned controller-gen artifact. Removed and regenerated docs/api/iam.md to drop the corresponding sections.

Test plan

  • kubectl kustomize config/crd/bases/iam builds cleanly and now produces 13 CRDs (was 12; PAA + 11 others; now PAA + PAR + 11 others; Denial removed entirely).
  • Searched the entire repo for PlatformAccessDenial / platformaccessdenial after the deletion: zero remaining references.
  • Existing CI checks pass.

@joggrbot
Copy link
Copy Markdown
Contributor

joggrbot Bot commented Apr 28, 2026

📝 Documentation Analysis

Joggr found 1 outdated docs in the pull request.

Autofix

Joggr opened 1 pull request(s) to fix the outdated docs.

Outdated

file reason confidence
docs/api/iam.md The document appears to describe 'PlatformAccessApproval' and 'PlatformAccessRejection' but makes no mention of 'PlatformAccessDenial', which was removed in the code. If PlatformAccessDenial was part of the public API previously, its removal and absence in documentation could indicate a significant misalignment, but if the doc already reflected the new state (i.e., no mention of PlatformAccessDenial), the impact is moderate. 61.5%

✅ Latest commit analyzed: 09366e0 | Powered by Joggr

@zachsmith1 zachsmith1 force-pushed the fix/iam-kustomization-missing-crds branch from 57b7575 to d987811 Compare April 28, 2026 00:31
@zachsmith1 zachsmith1 changed the title fix(iam): include PlatformAccessRejection and PlatformAccessDenial in CRD kustomization fix(iam): include PlatformAccessRejection in CRD kustomization Apr 28, 2026
@zachsmith1 zachsmith1 requested a review from scotwells April 28, 2026 00:33
…dead Denial CRD

Two related fixes to config/crd/bases/iam:

1. Add the missing iam.miloapis.com_platformaccessrejections.yaml entry
   to kustomization.yaml. PlatformAccessRejection was introduced in
   41e0bec alongside PlatformAccessApproval (the commit message reads
   "introduce platform access approval, rejection, and invitation
   resources"), but only the approval entry made it into kustomization.yaml.
   PAR has 120 Go references with a real controller and webhook, so it
   should be in the kustomization alongside PAA.

2. Delete the dead iam.miloapis.com_platformaccessdenials.yaml CRD
   manifest. PlatformAccessDenial has zero references anywhere in the
   milo Go codebase — no type, no controller, no webhook. It was an
   orphaned controller-gen artifact. Regenerated docs/api/iam.md to
   drop the corresponding sections.
@zachsmith1 zachsmith1 force-pushed the fix/iam-kustomization-missing-crds branch from d987811 to 09366e0 Compare April 28, 2026 00:37
@zachsmith1 zachsmith1 changed the title fix(iam): include PlatformAccessRejection in CRD kustomization fix(iam): include PlatformAccessRejection in CRD kustomization; drop dead Denial CRD Apr 28, 2026
@zachsmith1 zachsmith1 merged commit 1222dea into main Apr 28, 2026
10 of 12 checks passed
@zachsmith1 zachsmith1 deleted the fix/iam-kustomization-missing-crds branch April 28, 2026 00:53
zachsmith1 added a commit to datum-cloud/fraud that referenced this pull request Apr 28, 2026
datum-cloud/milo#580 is merged; the iam CRD kustomization on milo main
now includes platformaccessrejections.yaml, so install-milo-crds no
longer needs to fetch it via a separate raw-URL apply.
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.

2 participants