|
1 | 1 | # Copyright 2023 Canonical Ltd.
|
2 | 2 | # See LICENSE file for licensing details.
|
3 | 3 |
|
4 |
| -resume-upgrade: |
5 |
| - description: Upgrade remaining units (after you manually verified that upgraded units are healthy). |
| 4 | +pre-refresh-check: |
| 5 | + description: Check if charm is ready to refresh |
| 6 | +force-refresh-start: |
| 7 | + description: | |
| 8 | + Potential of data loss and downtime |
| 9 | + |
| 10 | + Force refresh of first unit |
| 11 | + |
| 12 | + Must run with at least one of the parameters `=false` |
6 | 13 | params:
|
7 |
| - force: |
| 14 | + check-compatibility: |
8 | 15 | type: boolean
|
9 |
| - default: false |
| 16 | + default: true |
10 | 17 | description: |
|
11 |
| - Potential of *data loss* and *downtime* |
| 18 | + Potential of data loss and downtime |
12 | 19 |
|
13 |
| - Force upgrade of next unit. |
| 20 | + If `false`, force refresh if new version of PostgreSQL and/or charm is not compatible with previous version |
| 21 | + run-pre-refresh-checks: |
| 22 | + type: boolean |
| 23 | + default: true |
| 24 | + description: | |
| 25 | + Potential of data loss and downtime |
| 26 | + |
| 27 | + If `false`, force refresh if app is unhealthy or not ready to refresh (and unit status shows "Pre-refresh check failed") |
| 28 | + check-workload-container: |
| 29 | + type: boolean |
| 30 | + default: true |
| 31 | + description: | |
| 32 | + Potential of data loss and downtime during and after refresh |
| 33 | + |
| 34 | + If `false`, allow refresh to PostgreSQL container version that has not been validated to work with the charm revision |
| 35 | + required: [] |
| 36 | +resume-refresh: |
| 37 | + description: | |
| 38 | + Refresh next unit(s) (after you have manually verified that refreshed units are healthy) |
| 39 | + |
| 40 | + If the `pause_after_unit_refresh` config is set to `all`, this action will refresh the next unit. |
| 41 | + |
| 42 | + If `pause_after_unit_refresh` is set to `first`, this action will refresh all remaining units. |
| 43 | + Exception: if automatic health checks fail after a unit has refreshed, the refresh will pause. |
| 44 | + |
| 45 | + If `pause_after_unit_refresh` is set to `none`, this action will have no effect unless it is called with `check-health-of-refreshed-units` as `false`. |
| 46 | + params: |
| 47 | + check-health-of-refreshed-units: |
| 48 | + type: boolean |
| 49 | + default: true |
| 50 | + description: | |
| 51 | + Potential of data loss and downtime |
| 52 | + |
| 53 | + If `false`, force refresh (of next unit) if 1 or more refreshed units are unhealthy |
14 | 54 |
|
15 |
| - Use to |
16 |
| - - force incompatible upgrade and/or |
17 |
| - - continue upgrade if 1+ upgraded units have non-active status |
| 55 | + Warning: if first unit to refresh is unhealthy, consider running `force-refresh-start` action on that unit instead of using this parameter. |
| 56 | + If first unit to refresh is unhealthy because compatibility checks, pre-refresh checks, or workload container checks are failing, this parameter is more destructive than the `force-refresh-start` action. |
18 | 57 | required: []
|
19 | 58 |
|
20 | 59 | set-tls-private-key:
|
|
0 commit comments