Project: mule
Issue MULE-8473: Configs should be optional when using Ext-api operations in a flow
Right now, every MP which executes an extension operation is required to provide a config. This is not good from a usability standpoint so the desired behaviour is: * If a config is specified through the config-ref attribute, then use it * If no config is specified but there's one configured, then locate it and use it * If no config is specified nor defined, then depending on the extension an implicit one can be created. An implicit configuration is created by simply instantiating the default config. Configs should be marked as not supporting implicit creation through some annotation/annotation attribute
Story points: 8