(website2 deployment) Removed min - max instances on the .yml file

[OchiengPaul442]

Summary of Changes (What does this PR do?)

• Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Status of maturity (all need to be checked before merging):

• I've tested this locally
• I consider this code done

Screenshots (optional)

Summary by CodeRabbit

• Chores
  • Updated the website’s automatic scaling behavior by removing preset limitations on service instances. This change empowers the system to dynamically adjust to varying traffic loads, potentially enhancing performance under high demand and providing a more responsive experience for users.
• Style
  • Improved the display formatting for comment content, ensuring consistency and clarity for a smoother user experience.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request removes the automatic scaling limits from the website2 deployment configuration. Specifically, it deletes the lines setting the minimum and maximum number of instances in the app.yaml file. Additionally, a minor formatting tweak was applied in the website2-pr-comment job to remove an extra space. There are no changes to any exported or public entities.

Changes

File	Change Summary
.github/.../deploy-frontend-pr-previews.yml	Removed the lines that set min_num_instances: 1 and max_num_instances: 3 in the website2 deployment job; adjusted a formatting issue in a comment job.

Possibly related PRs

• airqo-platform/AirQo-frontend#2425: Directly related removal of instance limits for automatic scaling in the app.yaml configuration.
• airqo-platform/AirQo-frontend#2421: Similar removal of the minimum instance configuration for website2 deployment.
• airqo-platform/AirQo-frontend#2409: Involves comparable changes to the scaling limits in the website2 app.yaml file.

Suggested reviewers

• Baalmart

Poem

In code’s quiet realm, a tweak takes flight,
Limits removed with a simple rewrite.
Deployment flows now free and clear,
With formatting fixed to end minor fear.
Cheers to progress in our techy sphere! 🎉

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

📜 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 1e8c6a3 and e670cf8.

📒 Files selected for processing (1)

• .github/workflows/deploy-frontend-pr-previews.yml (1 hunks)

🔇 Additional comments (2)

.github/workflows/deploy-frontend-pr-previews.yml (2)

646-668: Removed scaling limits for website2 deployment

The removal of the explicit min_num_instances: 1 and max_num_instances: 3 lines in the website2 app.yaml creation is consistent with the PR objective to allow a more flexible autoscaling behavior. Please verify that the default autoscaling settings (e.g., the specified CPU utilization target) are sufficient for your performance and cost requirements.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 649-649: trailing spaces

(trailing-spaces)

---

[error] 662-662: trailing spaces

(trailing-spaces)

---

696-710: Formatting cleanup in website2 preview comment

A minor formatting tweak was made in the website2 preview comment step, which removes an extra space before the closing bracket. This improves the consistency and readability of the generated comment text.

🧰 Tools

🪛 actionlint (1.7.4)

698-698: property "check" is not defined in object type {website2: {outputs: {}; result: string}}

(expression)

---

702-702: the runner of "actions/github-script@v6" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

---

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

• 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.
  • 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 or @coderabbitai title 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.