fix: ensure all prod/dev/uat deployments

[drtechie]

📋 Description

JIRA ID:
Always ensure production is set as true for production/uat deployments

---

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🛠 Refactor (change that is neither a fix nor a new feature)
• ⚙️ Config change (configuration file or build script updates)
• 📚 Documentation (updates to docs or readme)
• 🧪 Tests (adding new or updating existing tests)
• 🎨 UI/UX (changes that affect the user interface)
• 🚀 Performance (improves performance)
• 🧹 Chore (miscellaneous changes that don't modify src or test files)

Summary by CodeRabbit

• Chores
  • Updated environment settings to reflect production status.

[coderabbitai]

Walkthrough

The isProduction property in the common_ci.properties file was updated from false to true. No other properties or files were changed.

Changes

File(s)	Change Summary
src/main/environment/common_ci.properties	Changed isProduction property from false to true

Poem

The switch is flipped, the flag is true,
Production mode, we welcome you!
No more testing, time to shine,
Our code is ready, feeling fine.
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/main/environment/common_ci.properties (1)

171-171: Add explanatory comment: Clarify that isProduction=true is intended for Production and UAT environments, and that development environments must override it if needed.

Proposed diff:

- isProduction=true
+ # Enable production mode for Production and UAT; dev environments should override as needed
+ isProduction=true

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fcb10a7 and 0a7d194.

📒 Files selected for processing (1)

• src/main/environment/common_ci.properties (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Package-test
• GitHub Check: Analyze (java)
• GitHub Check: Build

🔇 Additional comments (1)

src/main/environment/common_ci.properties (1)

171-171:

❓ Verification inconclusive

Confirm environment-specific override: Ensure that setting isProduction=true in this common CI configuration does not unintentionally apply to development deployments—verify that dev environments use a separate properties file or override this flag appropriately.

Run this script to locate all occurrences and confirm proper overrides:

---

🏁 Script executed:

#!/bin/bash
# Search for references to isProduction across the codebase
rg -n 'isProduction' .

Length of output: 413

---

Verify isProduction override per environment
I ran a search (rg -n 'isProduction' .) and found:

• src/main/environment/common_ci.properties:171 → isProduction=true
• src/main/environment/common_example.properties:195 → isProduction=false
• CookieUtil.java reads this value via @Value("${isProduction}").

Confirm that your configuration only loads common_ci.properties in CI pipelines and that development runs load the example/dev properties (or another profile-specific file) to override isProduction=false. This ensures the flag isn’t unintentionally set to true in non-production environments.