Hi, On Wed, Jan 6, 2016 at 11:54 AM, Oliver Lietz <[email protected]> wrote: > On Wednesday 06 January 2016 11:33:03 Bertrand Delacretaz wrote: >>... a) tweak the provisioning model tools so that a new ProvisioningModel >> service makes the content of :additional model sections available as >> unprocessed full text at runtime > > this is for auditing, right? Does it really help if ACLs can be changed in > several ways?...
Yes the idea is that one can later check if their instance is still compliant with the ACL setup of the provisioning model. Mostly to check that those ACLs have not been removed or changed by other means. I'm not planning to implement this right now but want to leave it open. >>... b) implement a component to process :basetree additional sections, >> with a micro-language to define the initial paths (with node types) to >> create for requirement 2) > > Does it need to be a _new_ micro-language or can we use the existing JSON and > XML formats?... Which existing languages exactly? At this point I'm thinking of a dead simple, one line per path format like CREATE [sling:Folder] /var/discovery[nt:unstructured]/some/subpath to mean "create the specified path, defaulting to sling:Folder unless bracketed nodetypes indicate otherwise. I think it matches the existing provisioning model "flavor" and that's simple to implement. > ...Please make sure we have an "API" for these components which can be used > when > not using the provisioning model.... Yes, I'm aiming for that and it's already the case for what's under contrib/extensions/acldef - feel free to yell if you see something missing. Thanks for the feedback, -Bertrand
