From: Krzysztof B. <go...@ic...> - 2015-06-12 09:04:15
|
Hi, W dniu 10.06.2015 o 12:12, Terefang Verigorn pisze: > Well, why at server startup? What is the use case? > > I'd prefer to add such feature to the REST API if you prefer to do > it in some automated way. Or there can be some bulk import/export > from UI (actually this is implemented, but only as a part of the > import/export of the whole database). I need to know your > requirements in more details first to suggest something concrete. > > > ok > > * use case #1: "Provisioning on Server Installation" > by installing a new instance, > i would like to create a number (~50) of attributes, > mostly coming from ldap-schema. > > * use case #2: "Provisioning on new Application Rollout" > having developed a new application that needs additional attributes, > or need to update an existing attribute enum, > or need to update an existing attribute regex-check > > > having attribute-definition in the rest api would actually be sufficient, > since one can package a script as part of the install or upgrade procedure. > > would this make it into 1.7.0 ? OK, so rest API is here a way to go. Note that 'loading on startup' is bit more confusing, as it work as expected during the first start and can mess your setup after subsequent restart (e.g. if you manually fixed one attribute type and then after restart you get the old definition). So yes, this is pretty easy to be added to the REST API, can go into 1.7.0. What is another low hanging fruit is a possibility to import attribute type definitions directly from LDAP schema. The converter is implemented in Unity but not exposed. I can enable it if you find this useful. Best, Krzysztof |