Skip to content

290 task remove scripts that do ipd functionality#293

Merged
Aravinda-HWK merged 4 commits intoLSFLK:mainfrom
maneeshaxyz:290-task-remove-scripts-that-do-ipd-functionality
Mar 12, 2026
Merged

290 task remove scripts that do ipd functionality#293
Aravinda-HWK merged 4 commits intoLSFLK:mainfrom
maneeshaxyz:290-task-remove-scripts-that-do-ipd-functionality

Conversation

@maneeshaxyz
Copy link
Copy Markdown
Member

@maneeshaxyz maneeshaxyz commented Mar 12, 2026

📌 Description


🔍 Changes Made

  • Remove add_user.sh
  • Format setup.sh
  • Remove Step 4: Initialize Thunder User Schema from start-silver.sh

✅ Checklist (Email System)

  • Core services tested (SMTP, IMAP, mail storage, end-to-end delivery)
  • Security & compliance verified (auth via Thunder IDP, TLS, DKIM/SPF/DMARC, spam/virus filtering)
  • Configuration & deployment checked (configs generated, Docker/Compose updated)
  • Reliability confirmed (error handling, logging, monitoring)
  • Documentation & usage notes updated (README, deployment, API)

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 simplifies the Silver Mail system's initial setup by decoupling user management functionality from the core mail service deployment. It removes a dedicated script for adding users and integrates with an Identity Provider (IDP), and streamlines the main setup script by eliminating a step related to IDP user schema initialization. This change focuses on making the mail system setup more concise and potentially shifts IDP-related user provisioning to a separate, external process.

Highlights

  • Removed Thunder IDP User Management Script: The add_user.sh script, which handled bulk user addition and Thunder IDP integration, has been completely removed.
  • Streamlined Silver Mail Setup: The start-silver.sh script no longer includes 'Step 4: Initialize Thunder User Schema', reducing the setup process from four steps to three.
  • Updated Setup Script Numbering: The step numbering in start-silver.sh has been adjusted to reflect the removal of the Thunder user schema initialization step.
Changelog
  • scripts/service/start-silver.sh
    • Removed 'Step 4: Initialize Thunder User Schema' section.
    • Updated step numbering from '1/4', '2/4', '3/4' to '1/3', '2/3', '3/3'.
    • Adjusted ASCII banner formatting by removing blank lines.
  • scripts/setup/setup.sh
    • Updated ASCII banner formatting by removing blank lines.
  • scripts/user/add_user.sh
    • Removed the entire script.
Activity
  • Closes issue [TASK] Remove scripts that do IPD functionality. #290.
  • Core services (SMTP, IMAP, mail storage, end-to-end delivery) have been tested.
  • Security and compliance (auth via Thunder IDP, TLS, DKIM/SPF/DMARC, spam/virus filtering) have been verified.
  • Configuration and deployment (configs generated, Docker/Compose updated) have been checked.
  • Reliability (error handling, logging, monitoring) has been confirmed.
  • Documentation and usage notes (README, deployment, API) have been updated.
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
Copy Markdown
Contributor

@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 removes functionality related to user management from setup scripts. Specifically, it removes the add_user.sh script entirely and the 'Initialize Thunder User Schema' step from start-silver.sh. These changes are accompanied by updates to step counters in the script's output and minor cosmetic cleanup of ASCII banners. The changes align with the goal of decoupling user management from the initial setup scripts. One suggestion is provided to improve the maintainability of the step-counting logic in start-silver.sh.

# Step 1: Domain Configuration
# ================================
echo -e "\n${YELLOW}Step 1/4: Configure domain name${NC}"
echo -e "\n${YELLOW}Step 1/3: Configure domain name${NC}"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

To improve maintainability, consider defining the total number of steps in a variable at the top of the script (e.g., TOTAL_STEPS=3). This would make it easier to update if steps are added or removed in the future, as you'd only need to change one value. This change should be applied to all step announcements in this script (steps 1/3, 2/3, and 3/3).

Copy link
Copy Markdown
Collaborator

@Aravinda-HWK Aravinda-HWK left a comment

Choose a reason for hiding this comment

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

LGTM

@Aravinda-HWK Aravinda-HWK merged commit 9dd1e4f into LSFLK:main Mar 12, 2026
6 checks passed
@Aravinda-HWK Aravinda-HWK deleted the 290-task-remove-scripts-that-do-ipd-functionality branch March 12, 2026 04:43
Aravinda-HWK pushed a commit that referenced this pull request Mar 17, 2026
* chore: remove Thunder Initialisation steps.

* chore: remove add_user.sh

* chore: fix format issue
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.

[TASK] Remove scripts that do IPD functionality.

2 participants