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

Proposal : Allowing service providers to specify to which plan(s), a particular plan is updateable to. #217

Open
prsahoo opened this issue Jun 5, 2017 · 5 comments
Assignees

Comments

@prsahoo
Copy link

prsahoo commented Jun 5, 2017

Problem

As a service provider, I want to be able to specify to which plan(s), a particular plan is updateable to. This will help provide a good and clear experience to the users.

Currently the users are allowed to go on a wrong path, and then the service broker gives the error message stating that the plan change is not valid. Instead the platform itself can restrict plan changes between incompatible plans, thus giving a good experience to the users.

Example

Consider a service broker having 4 plans.

Shared Small
Shared Medium
Shared Large
Dedicated

The service broker may want to explicitly specify that it permits plan upgrade from "Shared Small" to "Shared Medium" / "Shared Large" but not to the "Dedicated" plan.

Proposal

For the above scenario, I am proposing to add a field at the plan metadata level "updateable_to" where the service providers can specify an array of plans the particular plan is updateable to .

The platform can then restrict the users from attempting invalid plan changes.

@avade
Copy link
Contributor

avade commented Jun 5, 2017

Thanks for raising this issue @prsahoo.

I can see this being a useful addition to platforms waiting to provide an improved UX.

I wonder if this could be expressed as part of the plan schema or if we need to extend the spec for this use case.

@jmrodri
Copy link

jmrodri commented Jan 30, 2018

@duglin feel free to assign this issue to me, I will make a formal proposal document.

@duglin
Copy link
Contributor

duglin commented Jan 30, 2018

Bummer, I can't assign it to you so I picked Paul as the next best thing :-) hope that's ok.

@jmrodri
Copy link

jmrodri commented Jan 30, 2018

@duglin sure that's fine. @pmorie I'll take care of this.

@prsahoo
Copy link
Author

prsahoo commented Jan 30, 2018

Thanks @jmrodri . Please let me know if i can help in anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Inbox
Development

No branches or pull requests

5 participants