Building a Service Oriented CLI: Best Practices
summary
A production service (OCM) and its AWS-specific CLI (Rosa CLI) diverge when a new validating state is added to the service lifecycle; the CLI broke because it assumed the old initial state, forcing a compromised state order rather than shipping a new client to 100s of customers. Recommendation: keep the CLI thin, push business logic into the service, define a support two or three minor versions policy, and include automated CLI tests in CI to catch such regressions.
AI-written summary · about
chapters (5)
- 0:00CLI service story introduction
- 3:11Building CLI for RESTful service
- 6:19CLI versus service functionality
- 9:09Thin CLI architecture best practices
- 11:55Key takeaways and closing
related talks
26mBuilding Great CLI Experiences in Node
20mWhat makes a good CLI
33mCLI-Driven Developer Experience: The Secret Ingredient of an Aligned Team
16mHow Not To Build Your CLI’s
33mFrom OpenAPI to OpenCLI: AI-Ready Operations for Modern API Platforms
37mCLI's Aren't As Easy As You Might Think
16mBuilding an interactive CLI app in Elixir
38mSIG CLI Deep Dive