Ticket #953 (new Enhancement)
dm4-config: implement remaining roles of the configuration facility
Reported by: | Malte | Owned by: | |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.8 |
Component: | DeepaMehta Standard Distribution | Version: | 4.7 |
Keywords: | Cc: | jri | |
Complexity: | 3 | Area: | Application Framework / API |
Module: | deepamehta-config |
Description
This is a follow up to #830 and the aim would be now to release this as part of the 4.9.
As i understand from this part of the documentation my case is not yet fully supported so my next question consequently is: Can you already give an estimate about when the remainding roles will be implemented?
The remaining roles will be supported in DM 4.8. A rough estimation for the 4.8 release is end of february.
For some rough use case description see #822, #867.
The per-user configuration should also allow to store "sensitive" (in terms of "Private") information but i guess we got this covered already through the cores ACL mechanisms.
For a detailed description of the config facility, see:
https://trac.deepamehta.de/ticket/830#comment:20