Additional docs, fix import

Author: rtuck99

docs/developer/hyperion/hyperion-blueapi.rst

@@ -40,3 +40,26 @@ Launching
 ::
 
     ./run_hyperion.sh --beamline=i03 --dev --supervisor
+
+Configuration
+-------------
+
+Configuration of ``hyperion-blueapi`` and ``hyperion-supervisor`` is done via standard BlueAPI .yaml configuration files.
+Basic configuration files for i03 are supplied as follows in ``src/mx_bluesky/hyperion``.
+
+.. csv-table:: hyperion-blueapi configuration files
+    :widths: auto
+    :header: "File", "Description"
+
+    "blueapi_config.yaml", "Defines beamline device module and blueapi plans to be exported, BlueAPI REST to listen on, Stomp and graylog servers."
+
+
+.. csv-table:: hyperion-supervisor configuration files
+    :widths: auto
+    :header: "File", "Description"
+
+    "supervisor/client_config.yaml", "Tells the supervisor how to communicate with hyperion-blueapi, specifying the REST endpoint and stomp server."
+    "supervisor/supervisor_config.yaml", "Configures the internal blueapi context with a minimal beamline module containing the baton device and the graylog endpoint."
+
+When these are  deployed in kubernetes it is anticipated that these will be provided by specifying
+directly in the values.yaml which will be expanded by the base helmcharts at deployment time.

tests/system_tests/hyperion/supervisor/test_supervisor.py

@@ -21,7 +21,8 @@
 from mx_bluesky.hyperion.parameters.components import UDCCleanup
 from mx_bluesky.hyperion.plan_runner import PlanError
 from mx_bluesky.hyperion.supervisor import SupervisorRunner
-from unit_tests.hyperion.external_interaction.callbacks.test_alert_on_container_change import (
+
+from ....unit_tests.hyperion.external_interaction.callbacks.test_alert_on_container_change import (
     TEST_VISIT,
 )