[management-api] Upgrade a subscription

[NicolasGeraud]

I need to be able to move a subscription to another plan. With this feature, i can upgrade a consumer to another plan without forced the consumer to change its apikey

[pochadri]

+1

[icandir]

Hi Nicolas
What is the state of this issue?
I want to ask some questions about the feature if you could answer? Here they are.

• What is the main purpose of this feature?
• is it for moving the subscriptions to a new plan? or is it for changing the used API?
• As an example we have a plan of API A with version v1, and we are making a major change on this API (fixing a big bug), and let say we are going to change the API A version to v2. After this change there is no any API A with version v1 on our gateway. Then there is a mandatory action which should be taken by the api manager automatically or manually,
• This mandatory action could be taken manually, or automatically(when we are publishing the api A v2 the wizard may ask is this a version change first? if answer is YES, then another question could be asked as is this a major change then if we say YES again, the main question could be asked as Do u want to retire API A v1 and let Subscriptions moved to API A v2(YES) Or do u want to deploy API A v2 without moving the subscriptions of API A v1 to API A v2? (Also there could be another question to copy subscriptions of v1 to v2 without retiring v1)

[NicolasGeraud]

hi @icandir ,
as you can see (no milestone set), this issue is in the backlog and not schedule yet.

• The main purpose of this issue is to be able to move a subscription to another plan in the same api. As a consumer, let say you have subscribed to a low rate plan for cheaper price. You are satisfied by the service and want a better plan (with more quote for example). With this feature, the api owner can promote an app to another plan.

• I don't understand your example (I mean, from a business point of view). If you fix a bug, why do you need to change version number ?
  If you want to move all your consumers to the new Api, why not simply rename the first version of the API ?
  If you want to manage 2 version of your API, it probably means that your api contract has changed. So your consumer need to upgrade his code. In this case, it makes sense to have 2 different subscriptions.

What do you think ?

[icandir]

• ok the main purpose is different than. because this action is upgrading subscription plan.
  my purpose is to move the subscriptions of one api plan to the apis new version plan.

• I will reply second paragraph later.

[brasseld]

Hi @icandir any news about the second point ?

[NicolasGeraud]

I close this issue cause the main purpose of this issue will be resolved thanks to #1946