Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Add SSSDDomain.get_domain_options() and SSSDDomain.get_provider_options() #1357

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/315

  • Created at 2009-12-07 20:37:57 by sgallagh
  • Closed at 2020-03-24 14:23:30 as wontfix
  • Assigned to sgallagh

"The domain.list_provider_options() and domain.list_options() - I see
there is a partial duplication of options between these two calls. There
are a few questions to discuss - Wouldn't it make sense to have a call
which would list only non-provider options for a domain? I am currently
held on decision whether I should display all the options from
domain.list_options() or if I should display only the options returned
from domain.list_provider_options()." -- tmraz

We should add a call SSSDDomain.get_domain_options() and SSSDDomain.get_provider_options(,). These calls will return non-provider options and a specific provider's options, respectively.

Comments


Comment from sgallagh at 2010-02-23 15:03:08

Fields changed

milestone: SSSD 1.1 => SSSD Deferred


Comment from dpal at 2012-01-19 03:16:55

Fields changed

rhbz: => 0


Comment from sgallagh at 2017-02-24 14:59:19

Metadata Update from @sgallagh:

  • Issue assigned to sgallagh
  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:23:29

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.


Comment from pbrezina at 2020-03-24 14:23:30

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants