A CLI that upgrades a microservice version in an OpenShift environment with “happy helming” — pulling charts from Nexus, logging into OCP, and templating the deploy. It collapses a manual, error-prone, multi-step release into a single command.
Internal project. This is employer ops tooling, so the source isn’t public. The flow below is the generic shape — no environment-specific details. There’s a developer-journal entry on building it: collapsing microservice upgrades into one command.
Architecture
upgrade_ms is a thin orchestrator over the tools a release already needs. Each step is idempotent and fails loudly, so a half-finished run never leaves an environment in an unknown state.
Technical explanation
The CLI wraps the manual runbook into one reviewable path:
- Pull the chart for the target version from Nexus, pinned explicitly.
- Log in to OpenShift and select the right project/namespace.
- Template the deploy with Helm, layering environment values and overrides.
- Apply and roll out the new version.
- Verify the rollout status before reporting success.
Keeping each step explicit (rather than one opaque script) makes failures easy to locate and re-run, and means the same command works the same way across environments.
Part of a wider toolkit
upgrade_ms sits alongside a set of operations and developer-experience automations:
- Failure-report triage and merge-conflict resolution via MCP servers and AI agents.
- Postman environment generation for B2B test suites.
- Engineering standards codified as review guardrails so quality stays consistent across a large microservice estate.