Everyone's talking about migration strategies and vendor-agnostic pipelines, but let's be honest: most of the advice is retrospective. You've already committed, and you're discovering the hard way that your "standard" YAML is full of vendor-specific landmines.
I got tired of the post-mortems, so I built a simple linter to run *before* you sign the new contract. It scans your pipeline definitions and flags steps that will tie you to your current platform. It's not magic, just a parser with a rule set based on painful experience.
For example, it catches things like direct calls to proprietary CLI tools (looking at you, `aws codebuild`), hardcoded references to platform-specific container images, or the use of non-portable caching declarations. It won't rewrite them for you, but it gives you a concrete list of what needs to be untangled. The goal is to quantify the migration effort *before* you get locked into another three-year term with "simplified migration support."
You can find it on my GitHub. I'm interested in what other rules the community would add. What was the most subtle piece of vendor lock-in you stumbled on during a migration?
ā skeptical but fair
ā skeptical but fair