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
It makes a user not have to worry about what plugins are, so 'no fuss', although, you could be inadvertently loading/configuring some functionality without knowing it. Should we be more explicit with configs, requiring plugins that are depended on declared?
explicitly declare plugins?
As-Is
0%
explicitly declare (raise configuration error if plugin parameter is provided without the plugin specified)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
currently, the broker configuration is very forgiving when it comes to initializing plugins
even without specifying any auth (anonymous, password), amqtt loads both plugins.
if you specify the auth anonymous feature, it assumes you want the associated plugin loaded:
also, if you specify a sys_interval other than zero, it will assume you want to load the $SYS plugin loaded:
It makes a user not have to worry about what plugins are, so 'no fuss', although, you could be inadvertently loading/configuring some functionality without knowing it. Should we be more explicit with configs, requiring plugins that are depended on declared?
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions