You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: actions.yaml
+55-2Lines changed: 55 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,43 @@ create-replication:
18
18
type: string
19
19
description: The name of the replication (defaults to 'default').
20
20
default: default
21
+
force-refresh-start:
22
+
description: |
23
+
Potential of data loss and downtime
24
+
25
+
Force refresh of first unit
26
+
27
+
Must run with at least one of the parameters `=false`
28
+
params:
29
+
check-compatibility:
30
+
type: boolean
31
+
default: true
32
+
description: |
33
+
Potential of data loss and downtime
34
+
35
+
If `false`, force refresh if new version of PostgreSQL and/or charm is not compatible with previous version
36
+
run-pre-refresh-checks:
37
+
type: boolean
38
+
default: true
39
+
description: |
40
+
Potential of data loss and downtime
41
+
42
+
If `false`, force refresh if app is unhealthy or not ready to refresh (and unit status shows "Pre-refresh check failed")
43
+
check-workload-container:
44
+
type: boolean
45
+
default: true
46
+
description: |
47
+
Potential of data loss and downtime during and after refresh
48
+
49
+
If `false`, allow refresh to PostgreSQL container version that has not been validated to work with the charm revision
50
+
additionalProperties: false
21
51
get-primary:
22
52
description: Get the unit with is the primary/leader in the replication.
23
53
list-backups:
24
54
description: Lists backups in s3 storage in AWS.
25
-
pre-upgrade-check:
26
-
description: Run necessary pre-upgrade checks and preparations before executing a charm refresh.
55
+
pre-refresh-check:
56
+
description: Check if charm is ready to refresh
57
+
additionalProperties: false
27
58
promote-to-primary:
28
59
description: Promotes the cluster of choice to a primary cluster. Must be ran against the leader unit when promoting a cluster
29
60
or against the unit to be promoted within the cluster.
@@ -44,5 +75,27 @@ restore:
44
75
restore-to-time:
45
76
type: string
46
77
description: Point-in-time-recovery target in PSQL format.
78
+
resume-refresh:
79
+
description: |
80
+
Refresh next unit(s) (after you have manually verified that refreshed units are healthy)
81
+
82
+
If the `pause-after-unit-refresh` config is set to `all`, this action will refresh the next unit.
83
+
84
+
If `pause-after-unit-refresh` is set to `first`, this action will refresh all remaining units.
85
+
Exception: if automatic health checks fail after a unit has refreshed, the refresh will pause.
86
+
87
+
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`.
88
+
params:
89
+
check-health-of-refreshed-units:
90
+
type: boolean
91
+
default: true
92
+
description: |
93
+
Potential of data loss and downtime
94
+
95
+
If `false`, force refresh (of next unit) if 1 or more refreshed units are unhealthy
96
+
97
+
Warning: if first unit to refresh is unhealthy, consider running `force-refresh-start` action on that unit instead of using this parameter.
98
+
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.
99
+
additionalProperties: false
47
100
resume-upgrade:
48
101
description: Resume a rolling upgrade after asserting successful upgrade of a new revision.
0 commit comments