cf buildpacks should report whether buildpacks are "ready"

[cwlbraa]

What's the user value of this feature request?
This would help developers be aware of admin-managed buildpacks that can't actually be used at stage time.

Who is the functionality for?
App devs, mostly, as they may be unaware of admin-managed buildpacks left in unready states. Also useful for platform engineers as it'd provide a clearer indication that a given buildpack may not be consumable by appdevs.

Who else is affected by the change?
If people are making bad assumptions about the stability of cf buildpacks text output, this might be backwards-incompatible.

Is your feature request related to a problem? Please describe.
cloudfoundry/cloud_controller_ng#1625

Describe the solution you'd like

position   name                    stack        enabled   locked  state   filename
1          staticfile_buildpack    cflinuxfs3   true      false   READY   staticfile_buildpack-cflinuxfs3-v1.5.7.zip
2          staticfile_buildpack2   cflinuxfs3   true      false   AWAITING_UPLOAD   staticfile_buildpack-cflinuxfs3-v1.5.7.zip

Describe alternatives you've considered
We have considered not displaying unready buildpacks, but that might make it harder for platform operators to debug failed buildpack uploads.

Additional context
cloudfoundry/cloud_controller_ng#1625

@matt-royal

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/173299662

The labels on this github issue will be updated when the story is started.

[johha]

@cwlbraa Was this ever merged in? I tried cf buildpacks with cf version 8.4.0+b4c083e.2022-06-02 but there is no state column.

[philippthun]

"Re-opened": #2344