Upgrading AWS Glue environments has always been one of those tasks that looks simple on paper but turns into a maze of deprecated APIs, breaking changes, and compatibility headaches in practice. Now a developer is proposing a community skill for AWS Transform Custom that could automate much of the heavy lifting required to migrate repositories from Glue 2.0, 3.0, and 4.0 up to the upcoming Glue 5.0 release.

The Core Innovation: Separation of Concerns

The proposed tool takes a two-tier approach to migration work. First, it handles safe mechanical transformations automatically—things like updating import statements, adjusting deprecated function calls, and fixing version-specific configuration syntax. These are predictable changes that follow clear patterns and don't require human judgment. Second, the skill flags any modifications that genuinely need human review and evidence, surfacing them in a generated migration report rather than silently auto-fixing them. This design philosophy acknowledges that not everything should be blindly transformed during an upgrade. Some deprecated features might have been intentionally used with workarounds in place; others might be part of custom business logic that the automation shouldn't touch. By separating these concerns, the tool gives developers a clear picture of what's safe and what needs actual attention.

Preserving Already-Compatible Code

One practical detail worth noting: the skill preserves files that are already compatible with Glue 5.0 unchanged. This seems obvious in retrospect, but many upgrade tools tend to reformat or touch files even when no changes are necessary—adding noise to diffs and making code review harder than it needs to be. The author specifically designed the tool to leave untouched anything that's already working correctly under the new version's requirements.

Key Takeaways

  • Supports migration paths from Glue 2.0, 3.0, and 4.0 repositories to Glue 5.0
  • Automatically separates mechanical transformations from changes requiring human review
  • Generates a comprehensive migration report for manual verification
  • Preserves already-compatible files without modification to minimize diff noise

The Bottom Line

This kind of tooling is exactly what the AWS ecosystem needs more of—community-driven solutions that tackle real operational pain points. If this community skill gets traction, it could become the de facto way teams handle Glue upgrades instead of everyone reinventing their own migration scripts for each project.