-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Each setting type should have the ability to apply policies or read global information to use in the settings applyment phase.
There will be a global profile that will be applied to every machine, so it will be deployed on every login and saved by SSSD with an specified priority of 0 in each field and the name FleetCommander resulting in a file called:
000000_000000_000000_000000_000000_FleetCommander.profile
This file will contain settings as any other profile but under an special domain called org.freedesktop.FleetCommander
Each of the settings there will be a global setting or a policy for an specified kind of setting. For example, it can contain the policy for the NetworkManager connections for a profile that had been deleted and we want to delete the connection for users that had that connection applied in the past.
The example format for that data could be like this:
'org.freedesktop.FleetCommander: {
'policies': {
'PROFILE_UID': {
'org.freedesktop.NetworkManager': {
'flushOnProfileDelete': true
}
'com.google.Chrome': {
'managedBookmarkFolderName': 'HERE BE DRAGONS'
}
}
}
}
When the client reads the profiles, first it takes this data and load it to make it available for each config adapter.
Also we should add a method to base config adapter that handles the loading of each profile when merging all the data so the config adapter can decide what data is merged during that phase based on the policy for each profile.