fix: fixed application system api staging path

[brynjarorng]

...

Attach a link to issue if relevant

What

Specify what you're trying to achieve

Why

Specify why you need to achieve this

Screenshots / Gifs

Attach Screenshots / Gifs to help reviewers understand the scope of the pull request

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Formatting passes locally with my changes
• I have rebased against main before asking for a review

Summary by CodeRabbit

• New Features

  • Updated the staging configuration to point to the testing environment for the charge functionality.

• Bug Fixes

  • Corrected the endpoint path for the staging environment to ensure proper functionality during testing.

[coderabbitai]

Walkthrough

The changes involve updating the configuration for the XROAD_CHARGE_FJS_V2_PATH in both the application-system-api.ts and values.staging.yaml files. The path has been modified from the IS-DEV environment to the IS-TEST environment, indicating a transition from a development context to a testing context for the staging configuration. Other environment paths remain unchanged.

Changes

File	Change Summary
apps/application-system/api/infra/application-system-api.ts charts/islandis/values.staging.yaml	Updated XROAD_CHARGE_FJS_V2_PATH from 'IS-DEV/GOV/10021/FJS-Public/chargeFJS_v2' to 'IS-TEST/GOV/10021/FJS-Public/chargeFJS_v2'.

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.

---

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 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 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.

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.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7c9c1e5 and 82d3e97.

Files selected for processing (2)

• apps/application-system/api/infra/application-system-api.ts (1 hunks)
• charts/islandis/values.staging.yaml (1 hunks)

Additional context used

Path-based instructions (1)

apps/application-system/api/infra/application-system-api.ts (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Additional comments not posted (2)

apps/application-system/api/infra/application-system-api.ts (1)

60-60: LGTM!

The change to the staging path for XROAD_CHARGE_FJS_V2_PATH looks good. It correctly updates the environment from IS-DEV to IS-TEST, indicating a shift from a development context to a testing context for the staging configuration.

charts/islandis/values.staging.yaml (1)

832-832: LGTM!

The change to XROAD_CHARGE_FJS_V2_PATH looks good. Updating the path from IS-DEV to IS-TEST for the staging configuration makes sense.