summaryrefslogtreecommitdiffstats
path: root/install/ui/automember.js
diff options
context:
space:
mode:
authorPetr Vobornik <pvoborni@redhat.com>2012-03-22 17:31:48 +0100
committerPetr Vobornik <pvoborni@redhat.com>2012-03-29 13:39:53 +0200
commit18a6ab356a159a88c5aab014f344eb14a9d38c81 (patch)
tree2bfa238383478b44615542e508b776065366a13e /install/ui/automember.js
parentbbe672a2aea1651a4a0eeca20b8339f0799f3431 (diff)
downloadfreeipa-18a6ab356a159a88c5aab014f344eb14a9d38c81.tar.gz
freeipa-18a6ab356a159a88c5aab014f344eb14a9d38c81.tar.xz
freeipa-18a6ab356a159a88c5aab014f344eb14a9d38c81.zip
Inter-facet expiration
Problem: When some facet perform action which modifies data, some other facet may become expired. Example: User modifies group's description. Now group search facet contains old data and has to be refreshed. Solution: New event was added to facet: on_update. It should be executed when facet performs action which modifies data ie: details facet update or add entry to dnsrecord. Then entity policies were introduced. Entity policies are a objects which are stored in entity.policies. They have similar function as facet_policies - performing communications and other functionality between facets. This way facets don't have to contain such logic and thus they aren't dependant on each other. This patch adds IPA.facet_update_policy, IPA.adder_facet_update_policy, IPA.search_facet_update_policy, IPA.details_facet_update_policy. IPA.facet_update_policy: On facets_created it bind itself to [current entity].[source facet].[event]. Default event is on_update. When the event is executed it sets expiration flag to [dest entity].[dest facet]. IPA.search_facet_update_policy: IPA.facet_update_policy where source facet = search, dest facet = details, dest entity = current entity. Its a default policy for updatein changes from search facet to details facet. Right now it isn't needed but it will be needed when action lists come to play. IPA.details_facet_update_policy: same as IPA.search_facet_update_policy just reversed. Very important. IPA.adder_facet_update_policy: similar functionality, just source of the event is dialog. Default event is added (new event in entity_adder_dialog). Entity policies should be specified in entity's spec object. If none are specified a default ones are used. Default policies are: IPA.search_facet_update_policy and IPA.details_facet_update_policy. https://fedorahosted.org/freeipa/ticket/2075
Diffstat (limited to 'install/ui/automember.js')
-rw-r--r--install/ui/automember.js13
1 files changed, 13 insertions, 0 deletions
diff --git a/install/ui/automember.js b/install/ui/automember.js
index a9812a71f..df285973d 100644
--- a/install/ui/automember.js
+++ b/install/ui/automember.js
@@ -33,6 +33,19 @@ IPA.automember.entity = function(spec) {
IPA.metadata.objects.automember.takes_params.push(pkey_attr);
IPA.metadata.objects.automember.primary_key = pkey_attr.name;
+ spec = spec || {};
+
+ spec.policies = spec.policies || [
+ IPA.facet_update_policy({
+ source_facet: 'usergrouprule',
+ dest_facet: 'searchgroup'
+ }),
+ IPA.facet_update_policy({
+ source_facet: 'hostgrouprule',
+ dest_facet: 'searchhostgroup'
+ })
+ ];
+
var that = IPA.entity(spec);
that.init = function() {