Skip to content

splitting set_server method into two methods.#204

Merged
spoore1 merged 1 commit intoSSSD:masterfrom
danlavu:sssd-failover-setup
Sep 15, 2025
Merged

splitting set_server method into two methods.#204
spoore1 merged 1 commit intoSSSD:masterfrom
danlavu:sssd-failover-setup

Conversation

@danlavu
Copy link
Contributor

@danlavu danlavu commented Sep 15, 2025

  • set_server
  • set_invalid_primary_server

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.

Summary of Changes

Hello @danlavu, 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 refactors a core server configuration method within the SSSD test framework. By splitting the set_server method into two specialized functions, one for setting a standard server and another for configuring an invalid primary server for failover tests, the change enhances code readability and maintainability. This separation clarifies the intent of each configuration action, making the codebase easier to understand and extend.

Highlights

  • Method Refactoring: The set_server method in sssd_test_framework/utils/sssd.py has been refactored into two distinct methods to improve clarity and separation of concerns.
  • New Method set_invalid_primary_server: A new method, set_invalid_primary_server, has been introduced to specifically handle the configuration of an invalid primary server and a valid backup server for failover testing scenarios.
  • Simplified set_server: The original set_server method now exclusively handles the configuration of a valid primary server, removing the failover parameter and its associated conditional logic.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 refactors the set_server method by splitting it into two more specific methods: set_server for setting a valid primary server, and set_invalid_primary_server for failover testing scenarios. This is a good improvement for code clarity and maintainability. I've added a few suggestions to further reduce some code duplication in the new methods and fix a minor typo in a docstring.

* set_server
* set_invalid_primary_server
@danlavu danlavu force-pushed the sssd-failover-setup branch from 12cf862 to e1c9cb4 Compare September 15, 2025 16:48
@danlavu
Copy link
Contributor Author

danlavu commented Sep 15, 2025

SSSD/sssd#8081 @jakub-vavra-cz @thalman suggested that the method was confusing.

Copy link
Contributor

@spoore1 spoore1 left a comment

Choose a reason for hiding this comment

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

LGTM.

@spoore1 spoore1 merged commit 61b683c into SSSD:master Sep 15, 2025
5 checks passed
@danlavu danlavu deleted the sssd-failover-setup branch December 1, 2025 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants