In 389-ds-base a new "data" directory (/ds/dirsrvtests/data) was created to store things like ldif files, backups, etc. To simplify automation and test execution a function to retrieve the full path to the data directory is necessary.
attachment 0001-Ticket-47851-Add-function-to-retrieve-dirsrvtests-da.patch
Thanks Noriko!
5cd2ce5..6fd3473 master -> master commit 6fd34730111545260a93b730b49e942edd6d13d1
We also need a temp directory, and a way to retrieve its path, to store things like exported ldifs, etc. Reopening ticket...
Use same fcuntion to get both data and tmp directories 0001-Ticket-47851-Need-to-retrieve-tmp-directory-path.patch
So, we can use "tmp". Nice!!
git merge ticket47851 Updating c0401ed..387135d Fast-forward lib389/init.py | 20 ++++++++++++++------ lib389/_constants.py | 2 ++
git push origin master c0401ed..387135d master -> master
commit 387135dd2cabaeab15b3a304daf0122e4efb831d
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1182
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.