Skip to content

AWS Transform Kiro Power sync (post cli-3.3.0) #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nadetastic merged 1 commit into from
Jul 1, 2026
Merged

AWS Transform Kiro Power sync (post cli-3.3.0) #158

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aws-transform/POWER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ displayName: "AWS Transform"
description: "Migrate, modernize, and upgrade codebases: .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server/Oracle/MySQL to Aurora, and Java/Python/Node.js version upgrades or AWS SDK migrations. Assess, plan, and execute code transformations from your IDE."
keywords: ["migrate", "modernize", "mainframe", "cobol", "vmware", "dotnet", ".net framework", "windows", "sql server", "oracle", "mysql", "aurora", "ec2 migration", "rehost", "lift-and-shift", "replatform", "legacy", "code upgrade", "sdk migration", "boto3", "java upgrade", "atx", "continuous modernization", "AWS Transform - continuous modernization"]
author: "AWS"
version: "2.1.2"
version: "2.2.0"
---

# AWS Transform Power
Expand Down
9 changes: 8 additions & 1 deletion aws-transform/steering/workload-continuous-modernization-batch-execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@ Show the list to the customer and ask:
3. **Repos to analyze:** all repos in source, or a specific subset
4. **Analysis type:** `tech-debt-comprehensive`, `tech-debt-quick`, `security`, `agentic-readiness`, `modernization-readiness`

If the list is empty or the customer wants to register a new source first, run `atx ct source add` via the [continuous-modernization-source](workload-continuous-modernization-source.md) skill, then return here.
If the list is empty, the customer wants to register a new source, or needs to update the token on an existing source, use the [continuous-modernization-source](workload-continuous-modernization-source.md) skill (`source add` for new, `source update` for existing), then return here.

Once the source is selected, run discovery and enumerate:

Expand Down Expand Up @@ -360,6 +360,13 @@ read -s TOKEN && { aws secretsmanager create-secret --name "<secret-name>" \
--secret-string "$TOKEN" --region <region>; }; unset TOKEN
```

- If the secret exists → ask the customer: "Your `<secret-name>` token was last updated on `<LastChangedDate>`. Would you like to rotate it, or is the current token still valid?" If they want to rotate:

```bash
read -s TOKEN && aws secretsmanager put-secret-value --secret-id "<secret-name>" \
--secret-string "$TOKEN" --region <region>; unset TOKEN
```

**Step B — Confirm SCM configuration with user (MANDATORY for non-local providers):**

Before submitting any batch job (analysis or remediation), ask the user to confirm the SCM provider config that will be injected into the container. An incorrect identifier, email, or username causes clone failures inside the container after the setup phase.
Expand Down
Loading