Wait for Stacks to attain State: Running
Before Continuing #27
Labels
No labels
availability
bug
deployment-usability
duplicate
enhancement
help-wanted
question
security
stack-auth
stack-chat
stack-cleanup
stack-git
stack-mesh
stack-site-support
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: python-support/python-support-infra#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Just like we do with DNS propogation, we should wait for the stack to actually run before moving on. This would ensure that other
role
s, ex. API-driven configuration of a newly-deployed service, are (mostly!) guaranteed to be able to talk to a thing that works - and that the user is more likely to be told when something happens that prevents the stack from actually running.stack deploy
has no mechanism for this, but anuntil
loop can get the job done. Thedocker_stack_info
module is also well-suited to scan for this information in anansible
-baseduntil
directive, just like in the DNS stacks.Here's the issue about this need (on CLI, not
ansible
, but they are related), with relevant inspiration: https://github.com/moby/moby/issues/30942