To date, we've been comingling the MEP and UEP configurations in Config. At this time, the two implementations are starting to diverge in their overlap, so bite the bullet and be clear about the differences. This implementation uses BaseConfig for the shared attributes, maintains Config for backward compatability, and introduces UserEndpointConfig for the user endpoint and ManagerEndpointConfig for the endpoint manager configuration.
The core of the changes start in endpoint/config/config.py, where UserEndpointConfig (for UEPs) and ManagerEndpointConfig (for MEPs) are defined. These are backed up by requisite changes to the Pydantic model in config/model.py, Just about every other change is in support of the now-distinct configuration classes.
Notes:
test coverage has increased around the configurations
the YAML facade shouldn't change at all from the user perspective. This is an internal organization detail
To date, we've been comingling the MEP and UEP configurations in
Config. At this time, the two implementations are starting to diverge in their overlap, so bite the bullet and be clear about the differences. This implementation usesBaseConfigfor the shared attributes, maintainsConfigfor backward compatability, and introducesUserEndpointConfigfor the user endpoint andManagerEndpointConfigfor the endpoint manager configuration.The core of the changes start in
endpoint/config/config.py, whereUserEndpointConfig(for UEPs) andManagerEndpointConfig(for MEPs) are defined. These are backed up by requisite changes to the Pydantic model inconfig/model.py, Just about every other change is in support of the now-distinct configuration classes.Notes:
[sc-37362]
Type of change