bmclib/internal/redfishwrapper
Jacob Weinstock d4ba0ef0f3 Use HTTP timeout for redfish:
In the gofish library all calls have to use the
same context that is only allowed to be defined
once with gofish.ConnectContext(). This means that
subsequent calls are bound to that context,
without the ability to modify it (the context field
in the APIClient is not exported and does not have a method to modify it).
This causes issues with "closing" a connection when a context
has timed out or been canceled. This call in redfish
is a call to the server to remove a session. This fixes orphaned
sessions that could lead to the max connections being
reached in the BMC and preventing future calls before the
timeout for these sessions is reached.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
2023-03-21 12:43:30 -06:00
..
boot_device.go Add redfish BootDeviceSet support 2023-01-13 16:01:06 -08:00
client_test.go redfish: adds an optional client parameter to specify incompatible Redfish versions 2023-01-30 14:11:58 +01:00
client.go Use HTTP timeout for redfish: 2023-03-21 12:43:30 -06:00
power.go redfish: use consistent case in method name 2022-11-30 18:21:54 +01:00
system.go internal/redfishwrapper: Add redfishwrapper client and methods 2022-11-30 18:21:52 +01:00
virtual_media.go Support redfish VirtualMedia 2023-02-09 15:36:40 -08:00