vmware-tanzu-labs/cf-mgmt

Org Metadata Update broken

kingdase opened this issue · 4 comments

kingdase commented

cf-mgmt is reporting "Your deployment does not yet support v3 metadata api"

The problem is, that the cloud controller is reporting version "3.101.0"

The source is comparing "3.101.0" with "3.66.0" which will fail.

cf curl "/"
{
   "links": {
      "self": {
         "href": "https://api.sys.box.aws.XXX.XXX.com"
      },
      "bits_service": null,
      "cloud_controller_v2": {
         "href": "https://api.sys.box.aws.XXX.XXX.com/v2",
         "meta": {
            "version": "2.166.0"
         }
      },
      "cloud_controller_v3": {
         "href": "https://api.sys.box.aws.XXX.XXX.com/v3",
         "meta": {
            "version": "3.101.0"
         }
      },
...
cf-gitbot commented

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

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

mstergianis commented

Hey @kingdase. I went ahead and fixed the issue. But in future please report issues on the project that is actually responsible. This was a bug in go-cfclient, not cf-mgmt. At this point, the resolution for this bug will be updating the library that we use. I'll keep this issue open to track the library update that is needed.

cramX commented

Hello,

is it possible to publish a new release in which the bugfix is included?

The issue was apparently already merged on 23.08.

Kind Regards

mstergianis commented

Thanks for keeping me honest @cramX 😄 . I've created 1.0.50