#2336 Refactor sdap_attr_map to contain the map and the count in one structure
Closed: wontfix 2 years ago by pbrezina. Opened 8 years ago by jhrozek.

Currently the sdap_attr_map is an array of map elements, the size is known with an enum sentinel. However, since the maps are extensible these days, it would be more practical to carry the element count inside the map itself.

The structure sdap_attr_map would be renamed to sdap_attr_map_el and the new sdap_attr_map would be defined as:

struct sdap_attr_map {
  size_t count;
  struct sdap_attr_map_el *map;

Then we would be sure we are using the right count without checking if the map was resized by the user or not.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

rhbz: => 0

Fields changed

mark: => 0

Perhaps in the scope of the LDAP provider refactoring..

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => minor

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

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

5 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 testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

2 years 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)

2 years 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/3378

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.