remove redundant/unnecessary variables from sample.env

Walkthrough

This update enhances environment variable management across various configuration files, focusing on improved clarity and alignment with new services. Key modifications include renaming user-related variables and updating scripts to accept multiple directory inputs, thereby increasing flexibility and robustness. These changes foster better configuration practices and adaptability within the system.

Changes

Files	Change Summary
`.github/workflows/pre-merge.yaml`	Updated command in the "Run custom update script" job to include additional arguments for enhanced script execution context.
`bhasai/yt_parser/docker-compose.SDC.yaml`, `bhasai/yt_parser/docker-compose.yaml`, `bhasai/yt_parser/sample.env`	Renamed environment variables from `BHASHINI_USERID` and `BHASHINI_ULCA_API_KEY` to `ULCA_USER_ID` and `ULCA_API_KEY`, enhancing clarity and alignment with new configurations.
`bhasai/bff/docker-compose.SDC.yaml`, `bhasai/bff/docker-compose.yaml`, `bhasai/bff/sample.env`	Changed `USER_SERVICE_ADMIN_API_KEY` to reference `ADMIN_API_KEY`, simplifying variable names and potentially improving access control.
`bhasai/admin/docker-compose.SDC.yaml`, `bhasai/admin/docker-compose.yaml`, `bhasai/admin/sample.env`	Updated `NEXT_PUBLIC_FLOWISE_URL` to dynamically construct the URL using `DOMAIN_SCHEME` and `DOMAIN_NAME`, enhancing clarity. Removed deprecated `NEXT_PUBLIC_FLOWISE_URL` from sample.env.
`sample.env`	Removed several environment variables, indicating a shift in configuration management or service utilization.
`scripts/generate-combined-sample-env.sh`	Modified script to accept multiple directories as input, improving error handling and script flexibility.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Script
    participant Directory

    User->>Script: Input directories
    Script->>Directory: Check existence of each directory
    Directory-->>Script: Return status (exists / not exists)
    Script->>Script: Process valid directories

🐰 In fields of green, we hop with glee,
New names and paths make us so free!
The script now leaps through directories wide,
With every check, we take in stride!
A spring in our step, we dance with delight,
For changes bring joy, oh what a sight! 🌼✨

[!NOTE]

Summarized by CodeRabbit Free
Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting .

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

BharatSahAIyak / devops