it would be very convenient, if the plugin adapters init method would also deliver the pluginId. Currently it seems that among some other data, one can only retrieve the tenantId and the pluginInstanceId. Is there anything that would speak up against adding the pluginId to the init response? Would be great.
Our current workaround is an extra endpoint in our plugin host backend database to get the pluginId, which is needed for further requests. But we are not too sure if the mapping (tenantId, pluginInstanceId) -> (pluginId) is unique, which forces us to pick the first match in our database.