Issue #3636: No use case for idrange-mod with --dom-sid and --dom-name - freeipa

freeipa

#3636 No use case for idrange-mod with --dom-sid and --dom-name

Closed: Fixed None Opened 10 years ago by steeve.

If the domain SID for an idrange must be changed, it is better to remove the old range and add new range. These options may not serve any purpose, so it will be better to remove them from idrange-mod.

mkosek commented 10 years ago

We will not remove the params from API but rather mark them as deprecated (see DeprecatedParam).

mkosek commented 10 years ago

master: b1321e9

mkosek commented 10 years ago

Rename "trusts" component to "Trusts" to achieve correct sorting.

Metadata Update from @steeve:
- Issue assigned to akrivoka
- Issue set to the milestone: FreeIPA 3.3 - 2013/05

7 years ago

Metadata

Assignee

akrivoka

Tags

None

Blocking

None

Depending on

None

Priority

low

Milestone

FreeIPA 3.3 - 2013/05

None

affects_doc

None

source

None

knownissue

None

type

defect

blockedby

None

test_case

None

component

Trusts

blocking

None

on_review

keywords

None

test_coverage

None

reviewer

None

external_tracker

None

rhbz

tester

None

changelog

None

design

None

freeipa

Source Code

#3636 No use case for idrange-mod with --dom-sid and --dom-name Closed: Fixed None Opened 10 years ago by steeve.

Metadata

#3636 No use case for idrange-mod with --dom-sid and --dom-name

Closed: Fixed None Opened 10 years ago by steeve.