Unknown health check type: none in v. 3.15.0

[robachmann]

Although it seems to be fixed in 8692982 (as reported in #909), I get the following exception when a process has a (v2) health-check of type none:

2019-07-31 17:09:53.484 ERROR 11315 --- [ry-client-nio-6] cloudfoundry-client.response             : Cannot construct instance of `org.cloudfoundry.client.v3.processes.HealthCheckType`, problem: Unknown health check type: none
 at [Source: (byte[])"{
  "pagination": {
    "total_results": 1,
    "total_pages": 1,
    "first": {
      "href": "https://api.company.com/v3/processes?app_guids=9a749a89-de8a-46c2-9d35-9739b0df309e&page=1&per_page=50"
    },
    "last": {
      "href": "https://api.company.com/v3/processes?app_guids=9a749a89-de8a-46c2-9d35-9739b0df309e&page=1&per_page=50"
    },
    "next": null,
    "previous": null
  },
  "resources": [
    {
      "guid": "4a9a871a-bcd0-42e3-93b5-8e32281b0ad6",
  "[truncated 1304 bytes]; line: 23, column: 17] (through reference chain: org.cloudfoundry.client.v3.processes.ListProcessesResponse$Json["resources"]->java.util.ArrayList[0]->org.cloudfoundry.client.v3.processes.ProcessResource$Json["health_check"]->org.cloudfoundry.client.v3.processes.HealthCheck$Json["type"])
{
  "pagination": {
    "total_results": 1,
    "total_pages": 1,
    "first": {
      "href": "https://api.company.com/v3/processes?app_guids=9a749a89-de8a-46c2-9d35-9739b0df309e&page=1&per_page=50"
    },
    "last": {
      "href": "https://api.company.com/v3/processes?app_guids=9a749a89-de8a-46c2-9d35-9739b0df309e&page=1&per_page=50"
    },
    "next": null,
    "previous": null
  },
  "resources": [
    {
      "guid": "4a9a871a-bcd0-42e3-93b5-8e32281b0ad6",
      "type": "web",
      "command": "[PRIVATE DATA HIDDEN IN LISTS]",
      "instances": 1,
      "memory_in_mb": 64,
      "disk_in_mb": 1024,
      "health_check": {
        "type": "none",
        "data": {
          "timeout": null,
          "invocation_timeout": null
        }
      },
      "relationships": {
        "revision": null
      },
      "created_at": "2019-07-03T13:59:19Z",
      "updated_at": "2019-07-03T13:59:19Z",
      "metadata": {
        "labels": {

        },
        "annotations": {

        }
      },
      "links": {
        "self": {
          "href": "https://api.company.com/v3/processes/4a9a871a-bcd0-42e3-93b5-8e32281b0ad6"
        },
        "scale": {
          "href": "https://api.company.com/v3/processes/4a9a871a-bcd0-42e3-93b5-8e32281b0ad6/actions/scale",
          "method": "POST"
        },
        "app": {
          "href": "https://api.company.com/v3/apps/9a749a89-de8a-46c2-9d35-9739b0df309e"
        },
        "space": {
          "href": "https://api.company.com/v3/spaces/07022884-23bf-4a0e-8d83-79cf02194de8"
        },
        "stats": {
          "href": "https://api.company.com/v3/processes/4a9a871a-bcd0-42e3-93b5-8e32281b0ad6/stats"
        }
      }
    }
  ]
}

I got the result from this call:

reactorCloudFoundryClient.processes().list(ListProcessesRequest.builder().applicationId(appId).build()).subscribe()

Other responses/processes work fine and I'm using the most recent version (3.15.0.RELEASE).

Thanks for having a look at it.

[mcunninghamirl]

+1

[PG2000]

+1