Details
Description
- Decide if/how we can separate config/env/content, and with what 'scope'
- Decide if/how to handle runtime created nodes such as those listed in “patch.filter.skip.include” in bccm config, the node created by replication for locking, users, groups and permissions created on production, etc.
- Decide if/how to handle additional security constraints, e.g. dev/system lock down of specific properties/nodes (for example groovy upgrader scripts, scxml, (certain) domain rules, workflow, etc.)
Attachments
Issue Links
- causes
-
HCM-56 Enforce runtime configuration changes constraints
-
- Closed
-