Re: Issue with cf service plan name access and update


Ketaki Gadre <kets.gadre@...>
 

Hi Zach,

We are already using cf release greater than 255, I still see the same
issue. Any idea why this should be happening?

On Tue, Jul 18, 2017 at 4:22 AM, Zach Robinson <zrobinson(a)pivotal.io> wrote:

Hello Ketaki,

This is a known issue. When a plan is disabled it becomes "invisible" to
users. However, we don't remove existing service instances because this
would break existing apps. Ideally a user would then update to a new plan
that is supported by their marketplace. However, as you noted, the update
doesn't work because the user can no longer see the old plan.

We addressed this in this story https://www.pivotaltracker.
com/story/show/137123835 and the fix should be available in cf release
255 or greater.

-Zach

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.