Skip to content

fix(terraform): bring #58 into #78, fix the red tftest and correct the managed-scan README - #102

Merged
tim-thacker-nullify merged 5 commits into
fix/terraform-kms-image-regionfrom
fix/ncc78-review-feedback-r3
Sep 15, 2026
Merged

tim-thacker-nullify merged 5 commits into
fix/terraform-kms-image-regionfrom
fix/ncc78-review-feedback-r3

Conversation

@tim-thacker-nullify

@tim-thacker-nullify tim-thacker-nullify commented Sep 15, 2026 •

Copy link
Copy Markdown
Member

Claude

#100 was built on #98's pre-squash head and can't merge into the moved #78 (duplicate batch/jobs, 9 rules, red tftest). This rebuilds its surviving fixes on #78 (5e171a6) and fixes the round-2 findings.

Supersedes #100. Chart 0.2.0 bytes unchanged. Report: round2-connector-98-99.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

tim-thacker-nullify and others added 5 commits September 15, 2026 14:17
whiskeylotus's review on #58 (W58-2) flagged that the collector
ClusterRole grants 12 kinds main's collect.go never lists: jobs is
kept since the monorepo's fix/k8s-deployment-matching-review stack
(#12807, which #12830 sits on) starts collecting Jobs owned by a
CronJob; cronjobs, horizontalpodautoscalers, poddisruptionbudgets,
ingressclasses, storageclasses, csidrivers, runtimeclasses,
priorityclasses, flowschemas, certificatesigningrequests and
customresourcedefinitions are dropped -- no open collector change
reads any of them.

Verified against context/internal/cloudintegrations/k8sintegration/
collect/collect.go on both the monorepo's main and
fix/k8s-deployment-matching-review branches.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
#99 dropped the 11 never-collected kinds (cronjobs, HPA, PDB,
ingressclasses, storageclasses, csidrivers, runtimeclasses,
priorityclasses, flowschemas, certificatesigningrequests, CRDs) from the
Helm ClusterRole only. The Terraform collector roles in both trees still
granted them, so a k8s-resources install of #58 kept read access to kinds
no collector reads, and the two collector roles differed by those 11
kinds. jobs is kept. Helm (0.3.0), TF v5 and TF v6 now grant identical
kinds and verbs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…rraform collector roles)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- Resolve k8s-resources main.tf with #78's side: it adds enable_collector
  gating, preconditions and CLUSTER_NAME; the collector role rules equal #58's.
- Take #58's chart clusterrole.yaml byte-for-byte so both branches carry the
  same chart 0.4.0 bytes (the publish check rejects same-version drift).
- From #100: whole-statement IAM drift check, scripts/** path filter, and the
  access-analyzer:List* tftest assertion that #78 currently fails.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…s in managed-scan RBAC

- Drop the server-side Table fetch claim and the per-cluster opt-out claim:
  neither exists in the deployed collector or managed scan.
- Kinds-read row: identical from k8s-resources and chart 0.3.0; 0.2.0 grants extra kinds.
- Add the batch/jobs row managed_scan.tf already grants.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

1 participant