Website fix: Outdated config variable name

[BenjaminSsempala]

Summary of Changes (What does this PR do?)

• Website fix: Outdated config variable name

Summary by CodeRabbit

• Configuration Updates
  • Updated deployment workflow configuration parameters for website and website2
  • Renamed cool_down_period to cool_down_period_sec
  • Changed cooldown period value from 120s to 120 in deployment configurations

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request focuses on standardizing the cool_down_period configuration across multiple GitHub Actions workflow files for website deployments. The primary change involves renaming the parameter from cool_down_period to cool_down_period_sec and adjusting its value representation from a string with a unit suffix (e.g., 120s) to a numeric format (e.g., 120). This modification affects deployment configurations for website and website2 across three workflow files: PR previews, production, and staging deployments.

Changes

File	Change Summary
.github/workflows/deploy-frontend-pr-previews.yml	Renamed cool_down_period to cool_down_period_sec and updated value from 120s to 120.
.github/workflows/deploy-frontends-to-production.yml	Updated cool_down_period parameter naming and format from 120s to 120.
.github/workflows/deploy-frontends-to-staging.yml	Modified cool_down_period parameter configuration from 120s to 120.

Possibly related PRs

• App Engine optimisation: Reducing idle instances for app engine #2390: Adding automatic scaling configurations for website and website2.

Suggested reviewers

• Psalmz777
• Baalmart

Poem

Configs dance, parameters shift,
Seconds tick, workflows lift,
cool_down_period finds new grace,
In deployment's gentle embrace 🚀
Code evolves, smooth and light! ✨

---

📜 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 acedbc4 and f1a33e9.

📒 Files selected for processing (3)

• .github/workflows/deploy-frontend-pr-previews.yml (2 hunks)
• .github/workflows/deploy-frontends-to-production.yml (2 hunks)
• .github/workflows/deploy-frontends-to-staging.yml (2 hunks)

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

• .github/workflows/deploy-frontends-to-staging.yml
• .github/workflows/deploy-frontend-pr-previews.yml
• .github/workflows/deploy-frontends-to-production.yml

---

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.

[coderabbitai]

Actionable comments posted: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6558b79 and acedbc4.

📒 Files selected for processing (3)

• .github/workflows/deploy-frontend-pr-previews.yml (2 hunks)
• .github/workflows/deploy-frontends-to-production.yml (2 hunks)
• .github/workflows/deploy-frontends-to-staging.yml (2 hunks)

🔇 Additional comments (3)

.github/workflows/deploy-frontends-to-production.yml (1)

281-281: LGTM! Value format is correct.

The numeric format without the 's' suffix is the correct way to specify the cool-down period.

.github/workflows/deploy-frontends-to-staging.yml (1)

233-233: LGTM! Value format is correct.

The numeric format without the 's' suffix is the correct way to specify the cool-down period.

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

656-656: LGTM! Value format is correct.

The numeric format without the 's' suffix is the correct way to specify the cool-down period.