Incorrect dsconf argument descriptions

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49980

• Created at 2018-10-16 15:40:15 by mmuehlfeldrh
• Closed at 2019-02-04 02:36:44 as fixed
• Assigned to nobody

---

Issue Description

There are some incorrect descriptions in the new dsconf replication arguments:

# dsconf -D "cn=Directory Manager" ldap://server.example.com replication --help
...
 set-changelog       Delete the replication changelog. This will
                     invalidate any existing replication agreements
 get-changelog       Delete the replication changelog. This will
                     invalidate any existing replication agreements

# dsconf -D "cn=Directory Manager" ldap://server.example.com --help
...
 repl-tasks          Manage local (user/subtree) password policies

# dsconf -D "cn=Directory Manager" ldap://server.example.com repl-tasks --help
...
 abort-cleanallruv   Set an attribute in the replication winsync
                     agreement 

Package Version and Platform

389-ds-base-1.4.0.18-20181016gita8c37ead5.fc28.x86_64

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2018-10-17 00:59:25

@droideck Would you mind taking a look? I think this would be pretty simple. If you wanted @mmuehlfeldRH you could fix this one if you wanted to as I think the code/change is easy for the descriptions?

Thanks for your report :)

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2018-10-17 00:59:26

Metadata Update from @Firstyear:

• Custom field component adjusted to None
• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None

[389-ds-bot]

Comment from mmuehlfeldrh at 2018-10-17 09:48:14

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-17 18:16:12

Looks good, do you want me to merge it?

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-17 18:16:14

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to ack (was: None)

[389-ds-bot]

Comment from mmuehlfeldrh at 2018-10-18 13:05:58

Can you please merge it? I haven't done this yet and I don't know if I have write access to the repo.

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-18 14:55:25

Can you please merge it? I haven't done this yet and I don't know if I have write access to the repo.

No problem, I added to my my current replication PR. I will get it merged soon.

Thanks again!

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2019-02-04 02:36:45

I think this is resolved?

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2019-02-04 02:36:45

Metadata Update from @Firstyear:

• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)