Registering relation-changed, preventing to be stuck in 'waiting'…if secrets weren't there at 'start'.
Issue
Currently if secrets aren't available before the start event, the evaluation on _datbase_confg returns an empty value, leaving the unit in Waiting state. However, even if the secrets become available, there's no further evaluation on this condition.
Solution
As for now, a relation-changed event allows for re-evaluation of the condition. (
This shouldn't interfere with the single other event that's modifying the state, which is relation-broken)
NOTE: Purposefully not updating libs now. data_platform_llibs/data_interfaces v21 is broken, and the fix is just being merged.
Registering relation-changed, preventing to be stuck in 'waiting'…if secrets weren't there at 'start'.
Issue
Currently if secrets aren't available before the
start
event, the evaluation on_datbase_confg
returns an empty value, leaving the unit inWaiting
state. However, even if the secrets become available, there's no further evaluation on this condition.Solution
As for now, a
relation-changed
event allows for re-evaluation of the condition. ( This shouldn't interfere with the single other event that's modifying the state, which isrelation-broken
)NOTE: Purposefully not updating libs now.
data_platform_llibs/data_interfaces
v21 is broken, and the fix is just being merged.