#5193 Conflicting vault 'service' option.
Closed: Duplicate None Opened 8 years ago by edewata.

The existing vault 'service' option conflicts with the 'service' option that will be added automatically for vault members in ticket #5172. Deprecating the old option is not sufficient, it has to be removed from the API.

Command options:

    Str(
        'service?',
        cli_name='deprecated_service',
        doc=_('DEPRECATED: Service name of the service vault'),
    ),
    Str(
        'servicename?',
        cli_name='service',
        doc=_('Service name of the service vault'),
    ),

Vault members:

    attribute_members = {
        'owner': ['user', 'group', 'service'],
        'member': ['user', 'group', 'service'],
    }

It will generate the following error:

[Mon Aug 03 17:19:00.197040 2015] [wsgi:error] [pid 9409] ipa: ERROR: Failed to start IPA: cannot override NameSpace.service value Str('service?', cli_name='deprecated_service', doc=Gettext('DEPRECATED: Service name of the service vault', domain='ipa', localedir=None)) with Str('service*', alwaysask=True, cli_name='services', csv=True, doc=u'services to add', label=u'member service')

To provide backward compatibility, a new API needs to be added to rename the 'service' option and to add the 'service' member. The old API will be retained for backward compatibility. The CLI should be using the new API. This depends on the ability to rename CLI (ticket #5189).

Proposed milestone: 4.2.1


freeipa-edewata-0373-Fixed-conflicting-vault-service-option.patch
freeipa-edewata-0373-Fixed-conflicting-vault-service-option.patch

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: FreeIPA 4.2.1

7 years ago

Login to comment on this ticket.

Metadata