fix(ci): allowed to pass RapidAPI key via GitHub Secret.

[hwakabh]

Issue/PR link

closes: #357

What does this PR do?

Describe what changes you make in your branch:

• added RapidAPI key to GitHub Secret
• enabled to fetch the key in CI and passed it to Cloud Run

(Optional) Additional Contexts

Describe additional information for reviewers (i.e. What does not included)

• e2e testings are not included in this PR, since this requires merge into main to confirm changes would be applied

Summary by CodeRabbit

• New Features

  • Enhanced workflow capabilities by integrating the Rapid API service through a new environment variable, RAPID_API_KEY.

• Chores

  • Improved security and flexibility of the GitHub Actions workflow by utilizing repository secrets for API key management.

[coderabbitai]

Walkthrough

The changes introduce a new environment variable, RAPID_API_KEY, into the GitHub Actions workflow for enhanced integration with the Rapid API service. This key is sourced from repository secrets, improving security. Additionally, the code now enables fetching certification and project data dynamically from an external API, replacing previous fixture data and enhancing error handling for API requests.

Changes

Files	Change Summary
.github/workflows/backend.yaml	Added RAPID_API_KEY environment variable sourced from secrets; included in job environment.
.../api.js	Integrated axios for dynamic fetching of certification and project data from RapidAPI; removed fixture data.

Assessment against linked issues

Objective	Addressed	Explanation
Enable fetching Resume data from external API (#357)	✅
Improve error handling for API requests (#357)	✅
Include e2e testing in this PR (#357)	❌	E2E tests are not included in this PR.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c3a55a1 and 44fcf5f.

Files selected for processing (1)

• .github/workflows/backend.yaml (2 hunks)

Additional comments not posted (2)

.github/workflows/backend.yaml (2)

13-13: Securely added RAPID_API_KEY to the global environment.

The addition of RAPID_API_KEY sourced from GitHub Secrets enhances security and ensures the key is available to all jobs in the workflow.

---

68-68: Passed RAPID_API_KEY to the gh-pages-api-server service.

The inclusion of RAPID_API_KEY in the env_vars section ensures the key is available during deployment, facilitating integration with Rapid API services.