[RFE] Enable driver field for the api of service_providers

[Liu Xie]

I found the api of service_provider is:

RESOURCE_NAME = "service_provider"
COLLECTION_NAME = "%ss" % RESOURCE_NAME
SERVICE_ATTR = 'service_type'
PLUGIN_ATTR = 'plugin'
DRIVER_ATTR = 'driver'
EXT_ALIAS = 'service-type'

# Attribute Map for Service Provider Resource
# Allow read-only access
RESOURCE_ATTRIBUTE_MAP = {
    COLLECTION_NAME: {
        'service_type': {'allow_post': False, 'allow_put': False,
                         'is_visible': True},
        'name': {'allow_post': False, 'allow_put': False,
                 'is_visible': True},
        'default': {'allow_post': False, 'allow_put': False,
                    'is_visible': True},
    }
}

I found driver filed in the body of response of get_service_providers .Why is there no driver field in the api?

I think there will be some scenarios need to use this filed ：
when i create a body for service_profile, i need know the driver what would be used, like this:
{
    "service_profile": {
        "enabled": "true",
        "driver": "neutron_lbaas.drivers.octavia.driver.OctaviaDriver",
        "description": "Dummy profile",
        "metainfo": "{'foo': 'bar'}"
    }
}

[Hongbin Lu (hongbin.lu)]

It looks this is API enhancement request so I tagged this bug as RFE. Awaiting for Neutron Driver team to triage this bug.

[Miguel Lavalle (minsel)]

Thanks for submitting this RFE. Would you describe the use cases where this would be necessary? Aren't your use cases served by https://developer.openstack.org/api-ref/network/v2/index.html?expanded=show-flavor-details-detail,list-service-profiles-detail#networking-flavors-framework-v2-0-current-flavor-service-profile?

[Miguel Lavalle (minsel)]

Any interest in continuing this conversation?

[Miguel Lavalle (minsel)]

Haven't heard back from submitter in two months. Will mark it invalid. Please feel free to restore it in case there is interest in continuing this conversation