Details
-
Bug
-
Resolution: Done
-
Minor
-
None
-
2.6 ER2
-
None
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
Description
Cite from help message
application positional argument is application unique identifier. Allowed id's are:
Application internal id
User_key (API key)
App_id (from app_id/app_key pair)
Client ID (for OAuth and OpenID Connect authentication modes)
so user expects that Application Object will be searched by(in this order):
1. application ID
2. user key
3. app_id
4. client ID
But as you can see from example:
Here search is done by "user key"
$ 3scale application show 3scale 1110 ID NAME DESCRIPTION STATE ENABLED ACCOUNT_ID SERVICE_ID PLAN_ID USER_KEY APPLICATION_ID 1126 app1name app1 description suspended false 239 252 632 1110 (empty)
Here search is done by ID
$ 3scale application show 3scale 1126 ID NAME DESCRIPTION STATE ENABLED ACCOUNT_ID SERVICE_ID PLAN_ID USER_KEY APPLICATION_ID 1126 app1name app1 description suspended false 239 252 632 1110 (empty)
But there is object with ID == 1110
$ 3scale application list 3scale | grep 1110 1110 huhu1 live true 236 249 626
So in first case had bigger priority search by user key than by ID. But according help message search by ID should have bigger priority than search by user key.
$ 3scale application --version 0.12.3
