Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

config.changed trigger not triggering #16

Open
stub42 opened this issue Mar 4, 2019 · 1 comment
Open

config.changed trigger not triggering #16

stub42 opened this issue Mar 4, 2019 · 1 comment

Comments

@stub42
Copy link
Contributor

stub42 commented Mar 4, 2019

I have a trigger on config.changed, which is not firing:

reactive.register_trigger(when='config.changed', clear_flag='postgresql.configured')

I think this is because caas_base is initializing the flags on module import, rather than scheduling it for later using hookenv.atstart like the base layer does. At this point, none of the triggers are registered as none of the code in reactive/ has been discovered.

@johnsca
Copy link
Contributor

johnsca commented Mar 11, 2019

Rather than porting canonical/layer-basic#126 here and hoping it doesn't get out of sync again, maybe we should go ahead and move forward with pulling the flags into charms.reactive.

johnsca added a commit that referenced this issue Jul 12, 2019
Quicker fix than pulling the flags into the framework, but we should do
that eventually.

Fixes #16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants