Introduces the WEAVER_UNREGISTER_DROPPED_PROVIDERS variable. If set to "True", Weaver providers that are no longer working (not responding when deployed) and are not named in WEAVER_WPS_PROVIDERS will be unregistered. This is useful when deploying Weaver with fewer providers than a previous deployment.
For example, if the stack is deployed with the Weaver, Finch, and Raven components. Then later deployed with just Weaver and Raven, the Finch provider will be unregistered from weaver.
Previously, the Finch provider would have remained as a Weaver provider despite the fact that it has been removed from the stack.
Changes
Non-breaking changes
Adds an additional config option to unregister old weaver providers
Overview
Introduces the
WEAVER_UNREGISTER_DROPPED_PROVIDERSvariable. If set to "True", Weaver providers that are no longer working (not responding when deployed) and are not named inWEAVER_WPS_PROVIDERSwill be unregistered. This is useful when deploying Weaver with fewer providers than a previous deployment.For example, if the stack is deployed with the Weaver, Finch, and Raven components. Then later deployed with just Weaver and Raven, the Finch provider will be unregistered from weaver.
Previously, the Finch provider would have remained as a Weaver provider despite the fact that it has been removed from the stack.
Changes
Non-breaking changes
Breaking changes None
Related Issue / Discussion
Additional Information
Links to other issues or sources.
birdhouse_daccs_configs_branch: master birdhouse_skip_ci: false