Topics

What do admins expect to see in "cf marketplace?"

Oleksii Fedorov
 

Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team

Oleksii Fedorov
 

Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476

Norm Abramovitz
 

If you take the conservative approach it would be a breaking change. 

We have a tool that validates the CF environment after deployment. In our use case, the service exists with plans x, y, z but plan z is disabled.   As long as we can get enabled and disabled plans in some way. that would be good enough.




On Mon, Mar 25, 2019 at 3:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Norman Abramovitz
Technical Director
Stark & Wayne, LLC



Oleksii Fedorov
 

Of course, we’re just trying “to play the card” that the original behaviour was a bug in the first place.

As an admin, If you want to see enabled and disabled plans as a result of the same command, you should use `cf service-access` and **not** `cf marketplace`.

Best regards,
Oleksii

On Mon, Mar 25, 2019 at 3:05 PM Norm Abramovitz <norm@...> wrote:
If you take the conservative approach it would be a breaking change. 

We have a tool that validates the CF environment after deployment. In our use case, the service exists with plans x, y, z but plan z is disabled.   As long as we can get enabled and disabled plans in some way. that would be good enough.




On Mon, Mar 25, 2019 at 3:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Norman Abramovitz
Technical Director
Stark & Wayne, LLC





--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476

Oleksii Fedorov
 

Sorry, the calendar was all mixed up, it’s Thursday 28.03


On Mon, Mar 25, 2019 at 6:17 PM Oleksii Fedorov <ofedorov@...> wrote:
Of course, we’re just trying “to play the card” that the original behaviour was a bug in the first place.

As an admin, If you want to see enabled and disabled plans as a result of the same command, you should use `cf service-access` and **not** `cf marketplace`.

Best regards,
Oleksii

On Mon, Mar 25, 2019 at 3:05 PM Norm Abramovitz <norm@...> wrote:
If you take the conservative approach it would be a breaking change. 

We have a tool that validates the CF environment after deployment. In our use case, the service exists with plans x, y, z but plan z is disabled.   As long as we can get enabled and disabled plans in some way. that would be good enough.




On Mon, Mar 25, 2019 at 3:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Norman Abramovitz
Technical Director
Stark & Wayne, LLC





--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476

Dave Ashby
 

Can't talk now.

On Mar 26, 2019 6:02 AM, Oleksii Fedorov <ofedorov@...> wrote:
Sorry, the calendar was all mixed up, it’s Thursday 28.03

On Mon, Mar 25, 2019 at 6:17 PM Oleksii Fedorov <ofedorov@...> wrote:
Of course, we’re just trying “to play the card” that the original behaviour was a bug in the first place.

As an admin, If you want to see enabled and disabled plans as a result of the same command, you should use `cf service-access` and **not** `cf marketplace`.

Best regards,
Oleksii

On Mon, Mar 25, 2019 at 3:05 PM Norm Abramovitz <norm@...> wrote:
If you take the conservative approach it would be a breaking change. 

We have a tool that validates the CF environment after deployment. In our use case, the service exists with plans x, y, z but plan z is disabled.   As long as we can get enabled and disabled plans in some way. that would be good enough.




On Mon, Mar 25, 2019 at 3:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Norman Abramovitz
Technical Director
Stark & Wayne, LLC





--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476

Sascha Matzke
 

Hi,

I'm totally in favour of fixing this. The current behaviour always felt wrong and I'm looking forward to the change. 

Best,

Sascha

On Mon, Mar 25, 2019 at 11:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476


Oleksii Fedorov
 

Thank you all for your replies and input!

We’ve decided to go forward with treating this as a bug (and not an expected behaviour) and hence not a breaking change. 

Best regards,
Oleksii,
on behalf of SAPI team

PS: If somebody’s scripts/automations are still using `cf marketplace` to list non-available plans, use `cf service-access` instead.

On Tue, Mar 26, 2019 at 8:04 PM Sascha Matzke <sascha.matzke@...> wrote:
Hi,

I'm totally in favour of fixing this. The current behaviour always felt wrong and I'm looking forward to the change. 

Best,

Sascha

On Mon, Mar 25, 2019 at 11:25 AM Oleksii Fedorov <ofedorov@...> wrote:
Hey, friends!

Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this Thursday 25 Mar at 5pm ET.

If you have any concerns, please tell us!

Best regards,
Oleksii
on behalf of SAPI team


On Fri, Mar 15, 2019 at 12:04 PM Oleksii Fedorov <ofedorov@...> wrote:
Hello, folks!

We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967

We understand that this is just one side of the coin: some admins confused about output of cf marketplace including all the plans (even disabled ones).

The question is if we fix it and admins will see only plans that are “usable” in the current space, will you be confused by that new behaviour? Will it break any of your scripts?

We’re thinking it’s just a bug fix, but maybe it’s a breaking change. And we’re it actually makes sense to do it at all. What do you think?

Best regards, 
Oleksii, Niki, and Alex
on behalf of SAPI team



--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476




--
Oleksii Fedorov
Senior Software Engineer
Pivotal Labs, Berlin
DE: +49 15757 486 476