Backout actions.yaml as a tactical fix.
The current implementation forces a charm to define its own pause/resume actions and charm lint will fail if they do not. This breaks charms in an unpleasant way so instead work is ongoing to make pause/resume code standalone in this layer. For the moment backout actions to unbreak charms. Change-Id: I04f313097f632d7fa89e1734b966d12bda21656c
This commit is contained in:
parent
91caccf8e5
commit
36ab4e52cd
11
actions.yaml
11
actions.yaml
|
@ -1,11 +0,0 @@
|
|||
pause:
|
||||
description: |
|
||||
Pause services.
|
||||
If the deployment is clustered using the hacluster charm, the
|
||||
corresponding hacluster unit on the node must first be paused as well.
|
||||
Not doing so may lead to an interruption of service.
|
||||
resume:
|
||||
description: |
|
||||
Resume services.
|
||||
If the deployment is clustered using the hacluster charm, the
|
||||
corresponding hacluster unit on the node must be resumed as well.
|
Loading…
Reference in New Issue