Closed deiferni closed 5 years ago
Possible solution: only set registry value when the customer wants to customize the list. Otherwise fall back to programmatic default. That would eliminate the need to figure out if the list can be updated in an og.core
upgrade step (which imo is not so easily possible).
I'm planning on introducing a gever-side-only whitelist and a per policy blacklist to address this.
That would automatically add new entries on the GEVER side to the policies. Not sure if that is desired as new entries will most likely more and more specific and it would force us to keep the policies in sync all the time.
We currently need to double check in any case.
quick summary of discussion and proposed implementation:
Discussed this again, and I suggested an approach where we don't let policies override the entire set, but instead go with a default set (defined in Python code) that is added and subtracted from by whitelists and blacklists respectively, which are defined as registry settings.
Informally approved by @deiferni 😉
officeconnector_editable_types
is only defined in zcml, but not on theIOfficeConnectorSettings
interface.local dev, missing visio for fresh deployments:
our test
in prod for one customer: