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
{{ message }}
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
I have a trigger on config.changed, which is not firing:
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.
The text was updated successfully, but these errors were encountered: