We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Before
clever create -o <org_id> <app_name> clever link <org_id>/<app_name> clever addon link <addon_id>
After
clever create [-o (<org_id>|<org_name)] <app_name> clever link [-o (<org_id>|<org_name>)] (<app_id>|<app_name>) clever service link-addon (<addon_id>|<addon_name>) clever service link-app (<app_id>|<app_name>)
That would fix #51. The clever service stuff will happen in #55
clever service
The text was updated successfully, but these errors were encountered:
Use (app|orga|addon)IdOrName arguments and options in the CLI.
3cbdade
The goal is to allow the users to use names instead of ids for clarity, while letting the user use proper ids to avoid ambiguity. See #67
Let users use organisation names and ids in clever create and `clev…
clever create
d27325c
…er link`. See #67
Allow addon names in addition to addons ids in the clever addon com…
clever addon
81d2bba
…mands See #67
Merge pull request #72 from /issues/67
5bec0ec
More consistent handling of apps, orgas and addons ids / names
divarvel
No branches or pull requests
Before
After
That would fix #51.
The
clever service
stuff will happen in #55The text was updated successfully, but these errors were encountered: