Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion specification/resources/autoscale_pools/models/member.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,18 @@ properties:
example: 2020-07-28T18:00:00Z
health_status:
Comment thread
SSharma-10 marked this conversation as resolved.
type: string
Comment thread
SSharma-10 marked this conversation as resolved.
example: 'active'

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi shivani,
I ran the following request for healthy autoscale pool -http://127.0.0.1:8080/#tag/Droplet-Autoscale-Pools/operation/autoscalepools_list_members . I did not see null field of unhealthy_reason.

Can you pls confirm this is expected behaviour?
For unhealthy autoscale pools, I am seeing number of droplets is becoming 0.
Then I am not able to see the field again.

enum:
- healthy
- unhealthy
example: 'healthy'
description: The health status of the Droplet.
unhealthy_reason:
type: string
nullable: true
description: |
A human-readable description of why the Droplet is unhealthy. Returns
`null` when `health_status` is `healthy`.
example: 'Droplet failed health check'
status:
type: string
enum:
Expand All @@ -36,5 +46,6 @@ required:
- created_at
- updated_at
- health_status
- unhealthy_reason
- status
- current_utilization
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,7 @@ members_all:
created_at: 2020-11-19T20:27:18Z
updated_at: 2020-12-01T00:42:16Z
health_status: "healthy"
unhealthy_reason: null
status: "active"
current_utilization:
memory: 0.3588531587713522
Expand Down
Loading