Skip to content

Comments

Set a configurable client/server installation password#799

Merged
kostyanf14 merged 1 commit intoHCK-CI:masterfrom
menli820:VIRTWINKVM-1829
Nov 18, 2025
Merged

Set a configurable client/server installation password#799
kostyanf14 merged 1 commit intoHCK-CI:masterfrom
menli820:VIRTWINKVM-1829

Conversation

@menli820
Copy link
Contributor

@menli820 menli820 commented Nov 14, 2025

Set a configurable HLK-client and HLK-server
installation password.

depend on: HCK-CI/HLK-Setup-Scripts#27
HCK-CI/AutoHCK-Installer#44

@gemini-code-assist
Copy link

Summary of Changes

Hello @menli820, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the installation process for HLK (Hardware Lab Kit) environments by introducing a configurable password mechanism for both client and server installations. It updates the default password to 'Assentor01' and provides a flexible way to override this default by reading a password from an external args.ps1.example file, ensuring that installation passwords can be managed more securely and adapted to specific deployment needs.

Highlights

  • Configurable Installation Password: Introduced the ability to set a configurable installation password for both HLK-client and HLK-server components.
  • Default Password Update: Updated the default installation password from 'Qum5net.' to 'Assentor01' in config.json.
  • External Password Reading: Added a new Ruby method read_password_from_args to dynamically fetch the installation password from an args.ps1.example file, falling back to the configured default if not specified or empty.
  • Password Integration: Integrated the dynamically retrieved password into the answer files for both studio and client installations, allowing for consistent password application during setup.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a configurable installation password for HLK-client and HLK-server, with a new default. My review focuses on security and code quality. I've pointed out a security risk with the hardcoded default password in config.json. I've also suggested a significant refactoring of the new read_password_from_args method in lib/engines/hckinstall/hckinstall.rb to improve its efficiency, robustness, and to follow common conventions.

end

def read_password_from_args
args_file = "#{@hck_setup_scripts_path}/args.ps1.example"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to parse args.ps1.example. This is just an example and in this case we still duplicate knowlage about default password.

Currently, if you want to change password you have two places and args.ps1.example outside of this repo. Let's have one place for password, leave it only in config.json.

@kostyanf14
Copy link
Contributor

@menli820 General comments, please check rubocop, rspec and typecheck results after changes. You can find CI CLI in .github directory.

@menli820 menli820 marked this pull request as draft November 14, 2025 10:08
Set a configurable HLK-client and HLK-server
installation password, default to 'Assentor01'.

Signed-off-by: menli <menli@redhat.com>
@kostyanf14 kostyanf14 merged commit 869221d into HCK-CI:master Nov 18, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants