Affects Version/s: None
Fix Version/s: None
This is to improve the policy framework upgrade experience.
- When the agent runs it will override defaults in C for any attribute listed.
- When policy starts to evaluate it will override any of the values populated by the augments file if the policy has something defined.
- Augments overrides Defaults in C
- Policy overrides Augments
- Policy Always Wins
In order to support backwards compatibility and flexibility in specification of individual attributes a single variable per attribute approach has been selected. The naming convention is control_TYPE_ATTRIBUTE.
In the augments file (def.json) it looks like this:
For example the variable to control maxconnections in agent control would be def.control_agent_maxconnections. Overriding the MPF defaults via the augments file looks like this:
And the policy in bundle common def to default the value to 30 but allow overriding by the augments file looks like this: