lib/rtoolsHCK: Add no_studio mode support#82
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a no_studio mode to rtoolsHCK.rb, allowing the tool to run without initializing studio-related services. It adds manual checks across several methods to raise errors or return early when this mode is active. The review feedback suggests a more robust, centralized approach to handle studio-only methods within handle_action_exceptions using an allowed list of client actions, which would prevent potential NoMethodError exceptions on other unprotected studio-only methods.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
elizashurov
force-pushed
the
add-no-studio-mode
branch
from
0a0f28a to
f48e76b
Compare
Introduce a `no_studio` initialization option that allows creating an RToolsHCK instance without connecting to the HLK studio. In this mode, WinRM and toolsHCK setup is skipped on initialize and teardown, while studio-only methods (run_on_studio, reconnect, connection_check, close_and_shutdown) raise a clear error if called. Signed-off-by: Elizabeth Ashurov <eashurov@redhat.com>
…onse Fix run_on_machine to always include the content key in the JSON response, even when the command produces no output. Signed-off-by: Elizabeth Ashurov <eashurov@redhat.com>
elizashurov
force-pushed
the
add-no-studio-mode
branch
from
f48e76b to
a34122a
Compare
2 participants
Introduce a
no_studioinitialization option that allows creating an RToolsHCK instance without connecting to the HLK studio. In this mode, WinRM and toolsHCK setup is skipped on initialize and teardown, while studio-only methods (run_on_studio, reconnect, connection_check, close_and_shutdown) raise a clear error if called.Also fix run_on_machine to always include the content key in the JSON response, even when the command produces no output.