Updated QA in DB EXPORT IMPORT SCHEDULER

[ImeshRanawellaSG]

Summary by CodeRabbit

• Chores
  • Revised environment options for scheduled export/import tasks. The accepted selections have been updated to QA1 and QA2 with corresponding error messages to guide proper input.

[coderabbitai]

Walkthrough

This update modifies environment validation in the scheduler. The shell script now requires the TO_ENV variable to be either "QA1" or "QA2", with an updated error message. In parallel, the GitHub workflow input for toEnv has been adjusted to present these new options instead of the previous "QA" and "COOP_Test". Both changes maintain the existing control flow while aligning the environment selection criteria.

Changes

File(s)	Change Summary
.github/scripts/db_export_import_scheduler.sh .github/workflows/database_export_import_scheduler.yml	Updated environment names from "QA" and "COOP_Test" to "QA1" and "QA2". The shell script now validates against "QA1" or "QA2" and displays an updated error message, while the workflow dispatch input options are similarly revised.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant W as Workflow
    participant S as Scheduler Script

    U->>W: Trigger workflow with selected environment (toEnv)
    W->>S: Execute scheduler with provided toEnv value
    S->>S: Validate toEnv against allowed values ("QA1"/"QA2")
    alt toEnv is valid
        S->>W: Proceed with export/import scheduling
    else toEnv is invalid
        S->>U: Return error message and exit script
    end

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e59f83a and d555193.

📒 Files selected for processing (1)

• .github/workflows/database_export_import_scheduler.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/database_export_import_scheduler.yml

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 396823a and e59f83a.

📒 Files selected for processing (2)

• .github/scripts/db_export_import_scheduler.sh (1 hunks)
• .github/workflows/database_export_import_scheduler.yml (1 hunks)

🔇 Additional comments (1)

.github/scripts/db_export_import_scheduler.sh (1)

20-24: Environment Variable Validation Update

The updated check now properly restricts TO_ENV to only the allowed values ("QA1" or "QA2"), and the error message has been updated accordingly. This change aligns with the updated environment nomenclature. In the future, if additional environments might be included, consider a more extensible validation approach (e.g., using a regex or an array-based check).