Skip to content

fix(aws-transform): address CLI 3.24.0 review findings - #222

Merged
nadetastic merged 1 commit into
kirodotdev:mainfrom
saicharansm:release/aws-transform-2.9.1
Nov 20, 2026
Merged

nadetastic merged 1 commit into
kirodotdev:mainfrom
saicharansm:release/aws-transform-2.9.1

Conversation

@saicharansm

Copy link
Copy Markdown
Contributor

Follow-up to #220 with corrections for AWS Transform CLI 3.24.0 behavior and guidance.

Summary

  • Correct remediation scope and limits.
  • Clarify IAM, scheduling, and bucket guidance.
  • Refine AWS Health event handling.
  • Document EC2 defaults and prerequisites.
  • Add the CloudFormation preview handoff.
  • Replace telemetry values with public-safe placeholders.
  • Correct VMware polling and artifact behavior.

The corresponding portable-plugin update is awslabs/agent-plugins#305.

Validation

  • Confirmed parity for all 13 source files.
  • Passed JSON, formatting, and reference checks.
  • Passed targeted behavior checks.
  • Passed the full agent-plugin build.

Publish the validated source-first fixes for repository splitting,
executor permissions, preview ownership, AWS Health guidance, status
behavior, worker setup, VMware polling, and transformation placeholders.
Bump the Power version to 2.9.1. Distinguish missing AWS Health
prerequisites from throttled reads that provide no missing-item details.

Verification:
- exact parity for all 13 source files against internal source: passed
- POWER.md parity after removing the public version field: passed
- python3 -m json.tool for both changed policies: passed
- changed-file scope: POWER.md plus 13 source files
- aws-transform/POWER.md version 2.9.1: passed
- zerodebt-analysis-aws-health-readiness Power eval: 5/5 passed
- git diff --check: passed
@nadetastic
nadetastic merged commit b836238 into kirodotdev:main Nov 20, 2026
1 check 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.

2 participants