You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add support to create_client_with_vendor, plumb through
Trying to approach this as something that makes sense, in the general sense, even though this is the first use-case for it.
The motivator here is, since a Lite-On power shelf has no vendor details in the service root, the Redfish client cannot determine the vendor hardware type, so it defaults back to a `RedfishStandard` client, and not a `LiteOnPowerShelf` client.
This means that when the client calls `set_machine_password_policy`, it fails, because it's using the `RedfishStandard` implementation, and not the `LiteOnPowerShelf` implementation; the Lite-On imlpementation uses an `AccountService` call, and not the "default" `AccountLockoutCounterResetAfter` call).
So right now my choices are to either:
- Skip `set_machine_password_policy` entirely for power shelves.
- Introduce a way to set a specific vendor on a client, and bypass the service root check.
0 commit comments