With more users adopting the rolling deployment feature and clients (ex. CLI , Stratos and Apps Man) starting to consume the deployment API resource, teams are starting to discover limitations with the original functionality. This document focuses on pain points and proposed solutions related to communicating deployment states in a consumable and flexible way.
ssisil
commented
5 years ago
Last Call for Review
7/5/2019
Proposal Name
CAPI Deployment States
TL;DR Summary
With more users adopting the rolling deployment feature and clients (ex. CLI , Stratos and Apps Man) starting to consume the deployment API resource, teams are starting to discover limitations with the original functionality. This document focuses on pain points and proposed solutions related to communicating deployment states in a consumable and flexible way.
Proposal URL
https://docs.google.com/document/d/10VClD8M1yEptkrlKiQzQ_r3DT-JW9Et9xHCFaQdwKpA/edit?usp=sharing
Point of Contact
Scott Sisil - ssisil@pivotal.io