⚠️ Deprecate convert subcommand - #901
Conversation
Signed-off-by: Marek Aufart <maufart@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe ChangesConvert command deprecation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The convert command remains available while directing users to its replacement plugin, with no new user or production impact; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Test Coverage ReportTotal: 48.8% Per-package coverage
Full function-level detailsPosted by CI |
Deprecating
crane convert, that was replaced with a plugin https://github.com/migtools/crane-plugin-buildconfig-to-shipwright. The convert-related code might be deleted in following release, but now still work just with deprecation warning.New implementation example
Migrating a namespace with a Dockerfile-based BuildConfig from OpenShift to a Shipwright-enabled cluster:
Related to #367
Summary by CodeRabbit
convertcommand is now deprecated.crane-plugin-buildconfig-to-shipwrightplugin as the recommended replacement.