We do not always have access to working volume tatooing that our current build expects.
As a result, we should allow DS to "deploy" itself as an instance in container mode if it detects an empty instance directory.
This requires us to make a skeleton instance during our rpm build, and to package this as a skeleton. we can then use a --container flag on the cli to indicate we want this feature, and if we start with -D "path", where path is non-existant, we deploy the skeleton, and create our paths as needed.
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7.0
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @firstyear: - Issue status updated to: Open (was: Closed)
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
There have been many changes leading to 1.4.2 and I think this is now possible.
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/2272
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.