tree e483d86eda0d6fc34b44e193d8d43fa1e5985253
parent d250c5e471ceaabd6f22497005be9f5449c9a1b1
author David Tang <davtang@google.com> 1747672601 -0700
committer Copybara-Service <copybara-worker@google.com> 1747672656 -0700

Make ResourceType a required field in EM configs

In follow up cl/758720742 we will use ResourceType to determine subfru status instead of the IsSubFru ProbeV2 property. To support this change, we should enforce explicit definition of ResourceType in all EM configs. Previously, unconfigured ResourceType would lead to default behavior of treating the resource as a RESOURCE_TYPE_BOARD, to have better defined behavior, we now will fail tlBMC store creation if ResourceType is not defined or an unrecognized type.

Update all existing unit tests to now have ResourceType defined, add cases for errors

#tlbmc

PiperOrigin-RevId: 760657431
Change-Id: Ia316451a4971e87d0d50b6363d2d05f1a2623581