#1907 Split the man dyndns man page options into an included file
Closed: wontfix 7 months ago by pbrezina. Opened 7 years ago by jhrozek.

There is currently quite some code duplication between the IPA and AD manual pages when it comes to describing dynamic DNS options. However, reducing the duplication is not trivial because the options differ in default values.

I see two options:
1. (easy) - document the defaults directly with the option per-provider (Default: True (IPA provider, False (AD provider)).
2. leverage the stringparam parameter of xsltproc to parametrize the defaults.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => 0
type: defect => task

Should probably also drop the reference to v2 when referring to FreeIPA as well in the sssd_ipa man page in the dyndns_update option.

sssd-1.13.3-5.fc23.x86_64

changelog: =>
mark: => 0
sensitive: => 0

Replying to [comment:2 rcritten]:

Should probably also drop the reference to v2 when referring to FreeIPA as well in the sssd_ipa man page in the dyndns_update option.

sssd-1.13.3-5.fc23.x86_64

Fair comment, I sent a one-liner to sssd-devel since this ticket is scheduled for 1.15..

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

3 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

7 months ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

7 months ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2949

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata