New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename convert
to config
to align with compose v1 UX
#10214
Conversation
Codecov ReportBase: 73.89% // Head: 73.89% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## v2 #10214 +/- ##
=======================================
Coverage 73.89% 73.89%
=======================================
Files 2 2
Lines 272 272
=======================================
Hits 201 201
Misses 60 60
Partials 11 11 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
b695ece
to
b723790
Compare
What I did
renamed "convert" command to "config" to be aligned with Compose V1 UX
convert
was introduced by Cloud integration development as we translated the compose model into cloud provider custom format. It was later adopted as the basis forcompose config
implementation, but changing the command canonical name doesn't make sense for our users (thousands blogs, stackoverflow, ... mention use ofconfig
command)