Skip to content

Present cloudgov as an AWS governance CLI#42

Merged
stxkxs merged 1 commit into
mainfrom
aws-governance-framing
Jul 3, 2026
Merged

Present cloudgov as an AWS governance CLI#42
stxkxs merged 1 commit into
mainfrom
aws-governance-framing

Conversation

@stxkxs

@stxkxs stxkxs commented Jul 2, 2026

Copy link
Copy Markdown
Member

See commit message for full details.

Summary

  • README/CLAUDE.md/help text reframe the tool as AWS governance; multi-cloud promises removed while the thin provider seam stays
  • Test fixtures neutralized (gcp/azure mock providers → gamma/beta, gcloud → fakectl)
  • GCP/Azure secret-leak detection patterns deliberately kept — catching third-party creds in AWS resources is AWS governance

The org runs a single cloud substrate; cloudgov's surface now says so.
README and CLAUDE.md frame the tool as AWS governance (IAM, cost,
posture, drift) over AWS × Kubernetes — the seam-ready parity-matrix
columns and "adding GCP or Azure is additive" framing are gone, and
the provider registry is described as a design property of the tool
rather than a promise of other clouds. The registry.go "register here
once implemented" slot comments are removed; the Factory/Capable seam,
its tests, and the finding.Provider field stay — they're small, real,
and exercised.

Fixture and comment cleanup follows the same line: mock providers in
tests rename gcp→gamma / azure→beta (sort-order assertions preserved:
aws < beta < gamma), gcloud remediation fixtures become neutral
fakectl commands, the tags standard fixture uses k8s as its second
surface, and audit help text names S3 rather than S3/GCS.

Kept deliberately: the GCP service-account-key and Azure
connection-string secret-leak patterns — third-party credentials
leaking into AWS resources is exactly what an AWS governance tool
should catch.

Co-authored-by: stxkxsbot <275011021+stxkxsbot@users.noreply.github.com>
@stxkxs stxkxs marked this pull request as ready for review July 3, 2026 04:25
@stxkxs stxkxs merged commit b51a7c1 into main Jul 3, 2026
12 checks passed
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