Skip to content

Updated the prefix from "stg" to "dev" for the Development environment in the AWS infrastructure.#493

Merged
vladsha-dev merged 3 commits intomainfrom
update-the-prefix-from-stg-to-dev-for-the-development-environment
Jan 29, 2025
Merged

Updated the prefix from "stg" to "dev" for the Development environment in the AWS infrastructure.#493
vladsha-dev merged 3 commits intomainfrom
update-the-prefix-from-stg-to-dev-for-the-development-environment

Conversation

@vladsha-dev
Copy link
Contributor

Some of the resources related to the Development AWS environment still have the stg prefix, which can be confusing since we also have a Staging environment with the same prefix. To clarify the resource names, including the database instance, the prefix has been updated from stg to dev for the development environment.

@vladsha-dev vladsha-dev self-assigned this Jan 29, 2025
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:22 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:22 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:22 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:22 — with GitHub Actions Inactive
Copy link
Contributor

@roninzp roninzp left a comment

Choose a reason for hiding this comment

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

LGTM

@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:25 — with GitHub Actions Inactive
@barecheck
Copy link

barecheck bot commented Jan 29, 2025

React App | Jest test suite - Code coverage report

Total: 28.37%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

@coderabbitai
Copy link

coderabbitai bot commented Jan 29, 2025

Warning

Rate limit exceeded

@vladsha-dev has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 1da26d3 and 223ca44.

📒 Files selected for processing (1)
  • doc/release/RELEASE-NOTES.md (1 hunks)
📝 Walkthrough

Walkthrough

The pull request focuses on updating resource identifiers in the terraform-development.tfvars file to distinguish between development and staging environments. Specifically, the changes modify RDS database and Memcached instance identifiers by replacing the stg (staging) prefix with dev (development) prefix. This ensures clearer resource naming and prevents potential confusion between different AWS environment configurations.

Changes

File Change Summary
deployment/environments/terraform-development.tfvars - Updated rds_database_identifier from "opensupplyhub-enc-stg" to "opensupplyhub-enc-dev"
- Updated rds_final_snapshot_identifier from "opensupplyhub-rds-stg" to "opensupplyhub-rds-dev"
- Updated ec_memcached_identifier from "opensupplyhub-stg" to "opensupplyhub-dev"
doc/release/RELEASE-NOTES.md - Added detailed bugfix description for version 1.29.0 explaining resource naming changes

Possibly related PRs

Suggested reviewers

  • mazursasha1990
  • VadimKovalenkoSNF
  • roman-stolar
  • Innavin369

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Beta)
  • @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.

@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:27 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:27 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:27 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:27 — with GitHub Actions Inactive
@sonarqubecloud
Copy link

@barecheck
Copy link

barecheck bot commented Jan 29, 2025

Dedupe Hub App | Unittest test suite - Code coverage report

Total: 56.14%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:34 — with GitHub Actions Inactive
@barecheck
Copy link

barecheck bot commented Jan 29, 2025

Countries App | Unittest test suite - Code coverage report

Total: 100%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

@barecheck
Copy link

barecheck bot commented Jan 29, 2025

Contricleaner App | Unittest test suite - Code coverage report

Total: 98.91%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:39 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:40 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:40 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:40 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:40 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:43 — with GitHub Actions Inactive
@barecheck
Copy link

barecheck bot commented Jan 29, 2025

Django App | Unittest test suite - Code coverage report

Total: 80.38%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:49 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:49 — with GitHub Actions Inactive
@vladsha-dev vladsha-dev temporarily deployed to Quality Environment January 29, 2025 13:49 — with GitHub Actions Inactive
Copy link
Contributor

@mazursasha1990 mazursasha1990 left a comment

Choose a reason for hiding this comment

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

Approved.
Thank you!

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.

4 participants