Skip to content
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

Consistent naming for organisations, addons, apps. #67

Closed
divarvel opened this issue Jun 13, 2016 · 0 comments
Closed

Consistent naming for organisations, addons, apps. #67

divarvel opened this issue Jun 13, 2016 · 0 comments
Assignees
Milestone

Comments

@divarvel
Copy link
Contributor

divarvel commented Jun 13, 2016

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

@divarvel divarvel self-assigned this Jun 13, 2016
@divarvel divarvel added this to the 0.5.0 milestone Jun 13, 2016
divarvel added a commit that referenced this issue Jun 13, 2016
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
divarvel added a commit that referenced this issue Jun 13, 2016
More consistent handling of apps, orgas and addons ids / names
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant