feat: treat AWS/Azure/GCP equally with cross-cloud equivalence map and progressive cloud routing#33
Merged
Merged
Conversation
…de compliance counter
… drop skills.sh phrase - CLAUDE.md/CONTRIBUTING.md/PR-template: fix stale SKILL.md size (305), reconcile <300 target with the 500 CI gate, add code-intelligence-lsp.md to the file tree, align frontmatter/word-count/path checklist with validate.yml, mark CHANGELOG/version as CI-managed (not manual), and remove an internal tool name from the public review checklist. - tests/baseline-scenarios.md: point the provisioners guard at the existing anchor; note S3 use_lockfile (DynamoDB legacy). - SKILL.md: OpenTofu starts at 1.6 (no pre-1.6 release). - README.md: add Kiro (intro, Requirements, install block); credit multiple contributors in 'Why this skill'; drop the skills.sh phrase (npx skills add stays).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Gives AWS / Azure / GCP equal footing in the skill without tripling tokens. Keeps AWS snippets canonical (near-zero AWS regression), adds compact
AWS | Azure | GCPequivalence tables, and a single on-demand cross-cloud route (progressive disclosure).Changes
Minimum Viable Backend (AWS S3)->Choosing a Remote Backend, labeled the S3 block "AWS example", added aCross-cloud / provider mappingdiagnose row + route, generalized the Security "Do" line to name AWS Secrets Manager / Azure Key Vault / GCP Secret Manager. (302 -> 305 lines; gate is 500.)Choosing a Remote Backend(links to the existingBackend Locking Supporttable, no duplication),Cross-cloud equivalents(backend block / access control / remote-state data source),Bootstrap parity(versioning / encryption / public-access / auth).Cross-cloud resource map(engine-neutral DB families).Cross-cloud security map(secret manager / firewalling / identity / encryption).id-token: write), removed two staticAWS_ACCESS_KEY_IDexamples, fixed staledynamodb_table->use_lockfile(1.10+).Tests
tests/baseline-scenarios.md: Scenario 18 (Azure backend defaulting to AWS) + Scenario 19 (GCP module defaulting to AWS resources), each with Forbidden Signals.tests/rationalization-table.md: new surface row "defaults to AWS/S3 when user said Azure/GCP" + guard.tests/compliance-verification.md: de-hardcoded the scenario counter (was stuck at "8", already omitted scenario 17) to defer to baseline-scenarios.md.Verification
wc -l SKILL.md= 305 (< 500 warn); frontmatter OK; broken-link scan clean; all 6 new/linked anchors resolve.gcs; Azure DB secrets -> Key Vault; S3 state -> unchanged).Notes