Skip to content

Commit c035f88

Browse files
authored
Minor updates to deployment docs (#4184)
* Add last_status_change to api response * link Canary Deployments to docs-dev-guide
1 parent 1dbe7f7 commit c035f88

File tree

2 files changed

+8
-3
lines changed

2 files changed

+8
-3
lines changed

docs/v3/source/includes/api_resources/_deployments.erb

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,8 @@
66
"value": "ACTIVE",
77
"reason": "DEPLOYING",
88
"details": {
9-
"last_successful_healthcheck": "2018-04-25T22:42:10Z"
9+
"last_successful_healthcheck": "2018-04-25T22:42:10Z",
10+
"last_status_change": "2018-04-25T22:42:10Z"
1011
}
1112
},
1213
"strategy": "canary",
@@ -80,7 +81,11 @@
8081
"guid": "59c3d133-2b83-46f3-960e-7765a129aea4",
8182
"status": {
8283
"value": "FINALIZED",
83-
"reason": "DEPLOYED"
84+
"reason": "DEPLOYED",
85+
"details": {
86+
"last_successful_healthcheck": "2018-04-25T22:42:10Z",
87+
"last_status_change": "2018-04-25T22:42:10Z"
88+
}
8489
},
8590
"strategy": "rolling",
8691
"options" : {

docs/v3/source/includes/resources/deployments/_header.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ Deployment strategies supported:
1616
applications to be deployed without incurring downtime by gradually rolling out instances. Max-in-flight can be configured
1717
to specify how many instances are rolled out simultaneously.
1818

19-
* Canary deployments deploy a single instance and pause for user evaluation. If the canary instance is deemed successful, the deployment can be resumed via the [continue action](#continue-a-deployment). The deployment then continues like a rolling deployment. This feature is experimental and is subject to change.
19+
* [Canary deployments](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html#canary-deployment-process) deploy a single instance and pause for user evaluation. If the canary instance is deemed successful, the deployment can be resumed via the [continue action](#continue-a-deployment). The deployment then continues like a rolling deployment. This feature is experimental and is subject to change.

0 commit comments

Comments
 (0)