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

api switch support #28

Open
outscale-mgo opened this issue Aug 17, 2023 · 0 comments
Open

api switch support #28

outscale-mgo opened this issue Aug 17, 2023 · 0 comments

Comments

@outscale-mgo
Copy link
Contributor

outscale-mgo commented Aug 17, 2023

osc-cli need an api selection before making any call.

examples osc-cli api ReadVms here have api
oapi-cli remove the arguments, problem, we might at some points have more than one api (like fcu, lbu and so on)

it could be require like in osc-cli, but it doesn't make sense, as peoples make api separator like they make namespaces in OOP, thinking there will be name collision, but in reality, name collision never happen.

I mean sure at some points it might happen, but look at linux code source that is 20+M lines of code and still manage to avoid them with a language that doesn't support namespace.

And most Outscale calls are like ReadVms, ReadVolumes, if the api name was Volumes/Vms. then osc-cli vms read would make sense, but it's not.

Therefore we can safely assume that 99.9% of the time api specification will be useless, and be require only for peoples who think that name collision will happen, but, if we don't have it, peoples will be scare than something that never happen, will happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant