Developer builds AI agent to automate AWS-to-GKE app migration with human oversight

·2 views

A software developer created an AI-powered tool called a 'skill' for the Antigravity CLI (agy) to automate the refactoring of cloud-dependent codebases from AWS to Google Kubernetes Engine (GKE). The tool addresses common migration pain points such as hardcoded AWS credentials, proprietary SDK usage like boto3, and local disk storage incompatible with ephemeral Kubernetes pods. It works by scanning cloud dependencies, spawning parallel subagents to refactor code and infrastructure, and validating changes on a local Kubernetes cluster before deployment. A mandatory human-in-the-loop (HITL) approval gate is built in to prevent any unsupervised changes from reaching production environments. The approach contrasts with simple scripted find-and-replace methods by using an LLM agent capable of understanding semantic context and adapting to the current state of the codebase.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Split a Terraform Monolith into Smaller, Focused State Files

Large Terraform states can slow down plans, widen blast radius, and cause conflicts when multiple teams work simultaneously. The recommended approach is to group resources by lifecycle and ownership into logical boundaries such as networking, compute, application, and monitoring layers. Engineers can migrate resources between states without destroying them using the terraform state mv command, moving one logical group at a time and verifying plans after each step. Once split, cross-state dependencies must be rewired by replacing direct resource references with input variables and module outputs. Tools like remote state data sources or dependency management platforms can then be used to pass output values across the separate state files.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Large Terraform State Files Slow Teams Down and How to Fix Them

As Terraform projects grow, state files managing hundreds or thousands of resources cause plan times to balloon, with some users reporting 20–25 minutes for states containing around 2,900 resources. Every terraform plan refreshes all resources via API calls regardless of whether their configuration changed, creating a sequential bottleneck that worsens with each new resource added. Large shared states also trigger cloud API rate limits from providers like AWS, Azure, and GCP, sometimes causing plans to fail entirely due to throttling. Beyond performance, a single large state file creates a wide blast radius where unrelated resources can be accidentally modified or destroyed in the same apply. Splitting infrastructure into smaller, purpose-specific state files is identified as the structural solution, while proposals for partial-refresh features in Terraform and OpenTofu remain unimplemented.

0 comments Read more at DEV Community

ProgrammingHacker News ·

US Labor Share of Income Hits Lowest Level Since World War II

The share of national income going to workers in the United States has fallen to its lowest point in the post-World War II era, according to research published by the Federal Reserve Bank of New York. The decline has been particularly sharp following the COVID-19 pandemic. The findings suggest that a greater portion of economic output is now flowing to capital owners rather than to wage earners. This shift has significant implications for income inequality and the broader distribution of economic gains across American society.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

TRON Vanity Address Generator Lets Users Create Custom Crypto Wallet Addresses

A new tool at tronsec.io/app allows users to generate custom TRON wallet addresses that begin or end with a chosen pattern, such as a name or project ticker. Vanity addresses are standard blockchain wallets created by brute-forcing cryptographic key pairs until one matches the desired sequence, with no added security vulnerability. Proponents argue they offer practical benefits on the TRON network, including reduced phishing risk, easier visual verification, and brand recognition for projects and payment processors. The computational cost of generating such addresses rises sharply with each additional character, since TRON's Base58 encoding multiplies the search space by roughly 58 per character. Security experts advise users to ensure private keys are generated locally on their own device and never transmitted to an external server.

0 comments Read more at DEV Community