The prose says we want a conductor config override, but the example code implements a node-level override as well. We are only OK with implementing a conductor config override, but doing a node-level override is not a good idea because it's an API-exposed configuration without an API-exposed manner for that CA to go into place.
2:
The proposal wants to add [conductor]/default_verify_ca_path, but example code is for iRMC. If we are adding this config at [conductor], we must add support at a higher level than iRMC driver.
So going to clarify concerns here:
1:
The prose says we want a conductor config override, but the example code implements a node-level override as well. We are only OK with implementing a conductor config override, but doing a node-level override is not a good idea because it's an API-exposed configuration without an API-exposed manner for that CA to go into place.
2:
The proposal wants to add [conductor] /default_ verify_ ca_path, but example code is for iRMC. If we are adding this config at [conductor], we must add support at a higher level than iRMC driver.