← Back to branch summary

~pjdc/mojo/clarify-container-class-message

« back to all changes in this revision

Viewing changes to docs/mojo/readme.md

  • Committer: mergebot at canonical
  • Author(s): "Tom Haddon"
  • Date: 2020-07-06 07:04:06 UTC
  • mfrom: (557.2.2 wait-k8s)
  • Revision ID: mergebot@juju-139df4-prod-is-toolbox-0.canonical.com-20200706070406-gxg564p401dw8n3r
Add wait-for-workload as an option to juju-check-wait phase, defaulting to False



Reviewed-on: https://code.launchpad.net/~mthaddon/mojo/juju-check-wait-for-workload/+merge/386819
Reviewed-by: Stuart Bishop <stuart.bishop@canonical.com>

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/mojo/readme.md
755
755
        We check juju status after each deploy phase. How long in seconds
756
756
        before we timeout if instances remain in a pending status.
757
757
        Default: 1800 (30min)
 
758
      wait-for-workload=True/False
 
759
        Whether to wait for the workload to reach an active state. If set
 
760
        to False it does not pay attention to any workload state except
 
761
        'error', because charms are not required to set their state
 
762
        meaningfully.
 
763
        Default: False
758
764
 
759
765
<a id="phases-mojo-stop-on"></a>
760
766
### mojo stop-on ###