summaryrefslogtreecommitdiff
path: root/Pipfile.lock
diff options
context:
space:
mode:
authorEnrique Alcántara <ealcantara@gitlab.com>2019-04-26 08:15:44 +0000
committerPhil Hughes <me@iamphill.com>2019-04-26 08:15:44 +0000
commit690382dda6d7404d702276413f907d5744498fde (patch)
tree8eba5d2bc72923bde41a75582f970aa53a8bece2 /Pipfile.lock
parent336a0a8745e7eb1bb38c6f6f0ec7832569b041bf (diff)
downloadgitlab-ce-690382dda6d7404d702276413f907d5744498fde.tar.gz
Use a FSM to determine application next state
- Separate cluster application UI state from server-side app status - Use a state machine to determine cluster application next state - Instead of using two variables to keep track of when an app is installing or updating, just use the app status property and control server-side and user events using the FSM service.
Diffstat (limited to 'Pipfile.lock')
0 files changed, 0 insertions, 0 deletions