Positional argument does not exist for dsidm "modify" in v1.4.0.21
F29 v 1.4.0.21
Following steps from https://www.port389.org/docs/389ds/howto/quickstart.html
dsidm instance user: error: invalid choice: 'modify' (choose from 'list', 'get', 'get_dn', 'create', 'delete', 'lock', 'status', 'unlock')
No error and adding a description to Alice...
@mreynolds So this one is my fault. In the updated docs I put in a command that was commited just after the branch for 1.4.1. So the choice here is add a warning on the quickstart, or we can push the modify command back to the 1.4.0 branch. I think it's pretty safe to do, but it is a "feature not a fix". What do you think is the right thing to do here?
Metadata Update from @firstyear: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
PS: Long term better solutions is defaulting nsUserAccount to have nsMemberOf by default, and/or enabling memberOf by default on new installs.
Put it in 1.4.0. dsidm is not offically documented yet, so really we can still do whatever with it.
Whatever we want with it?!?!? SO MUCH POWER :)
(I'll backport the patch today and close this, thanks!)
@mreynolds PR is here https://pagure.io/389-ds-base/pull-request/50209
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3264
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.