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

ldifparser should sort entries #484

Closed
baszoetekouw opened this issue Dec 8, 2023 · 2 comments · Fixed by #486
Closed

ldifparser should sort entries #484

baszoetekouw opened this issue Dec 8, 2023 · 2 comments · Fixed by #486
Milestone

Comments

@baszoetekouw
Copy link
Member

It would be nice if ldifparser could sort the entires in a sensible way. That makes it a lot easier to inspect the diffs as a humas.
For bonus points, also add an option that removes "transient" fields like createTimestamp, entryCSN, entryUUID, modifiersName and modifiersTimestamp.

@baszoetekouw baszoetekouw moved this from New to Todo in SRAM development Dec 8, 2023
@mrvanes mrvanes moved this from Todo to To be tested in SRAM development Dec 18, 2023
@baszoetekouw baszoetekouw added this to the v30 milestone Jan 10, 2024
@baszoetekouw baszoetekouw moved this from To be tested to Being tested in SRAM development Jan 15, 2024
@baszoetekouw
Copy link
Member Author

This doesn't work correctly yet. To be specific, I would expect for ldifparser to sort by dn in such a way that all info for a service is clustered, and with a service, all info about a CO is clustered, etc.

Concretely, I would expect this command:

sudo slapcat -n1 | /opt/ldapmonitor/ldifparser.py |grep -v '^ '| awk -F, '{print $(NF-4) }'

to output a sorted list.

@baszoetekouw baszoetekouw reopened this Jan 15, 2024
@github-project-automation github-project-automation bot moved this from Being tested to New in SRAM development Jan 15, 2024
@baszoetekouw baszoetekouw moved this from New to Todo in SRAM development Jan 15, 2024
@baszoetekouw
Copy link
Member Author

ok, after actually deploying this to test/acc it works like a charm 🥇

@baszoetekouw baszoetekouw moved this from Todo to To be deployed in SRAM development Jan 15, 2024
@sram-project-automation sram-project-automation bot moved this from To be deployed to To be tested in SRAM development Jan 15, 2024
@baszoetekouw baszoetekouw moved this from To be tested to To be deployed in SRAM development Jan 15, 2024
@sram-deploy-tools-automation sram-deploy-tools-automation bot moved this from To be deployed to Done in SRAM development Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants