Skip to content

fix(config): replace proxy url#1604

Merged
baktun14 merged 4 commits intomainfrom
fix/provider-proxy-url
Jul 1, 2025
Merged

fix(config): replace proxy url#1604
baktun14 merged 4 commits intomainfrom
fix/provider-proxy-url

Conversation

@baktun14
Copy link
Contributor

@baktun14 baktun14 commented Jul 1, 2025

Summary by CodeRabbit

  • Chores
    • Added new environment variables for provider proxy URLs in the production and staging configurations.
    • Removed provider proxy URL variables from the default environment configuration.

@baktun14 baktun14 requested a review from a team as a code owner July 1, 2025 15:39
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 1, 2025

Walkthrough

Two new environment variables, NEXT_PUBLIC_PROVIDER_PROXY_URL_WS and NEXT_PUBLIC_PROVIDER_PROXY_URL, were added to both the production and staging environment configuration files with URLs pointing to the Akash network's console provider proxy. These two variables were removed from the base .env file. No other variables were changed.

Changes

File Change Summary
apps/deploy-web/env/.env.production Added two new environment variables for provider proxy URLs.
apps/deploy-web/env/.env.staging Added two new environment variables for provider proxy URLs.
apps/deploy-web/env/.env Removed two environment variables for provider proxy URLs.

Poem

Two new URLs in the env file hop,
Provider proxies ready, connections won't stop.
With webs and requests, our configs now grow,
The Akash network's proxy will help data flow.
But from the base, those vars did leap,
To staging and prod, their new home to keep.
🐇✨


📜 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 09755d6 and a151675.

📒 Files selected for processing (1)
  • apps/deploy-web/env/.env (0 hunks)
💤 Files with no reviewable changes (1)
  • apps/deploy-web/env/.env
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: validate (apps/deploy-web) / validate-unsafe
  • GitHub Check: validate / validate-app
  • GitHub Check: test-build
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/deploy-web/env/.env (1)

16-17: Confirm infra & docs are updated for the new /console-provider-proxy route (HTTP + WS)
Changing both HTTP and WebSocket proxy prefixes means every place that terminates or rewrites these paths (k8s Ingress, CloudFront, Nginx, local next.config.js, etc.) must now be aware of /console-provider-proxy. Make sure:
• All environments (dev, staging, prod) expose the new path and still forward Upgrade: websocket headers correctly.
• Any hard-coded URLs in scripts, CI/CD, or docs are updated or will fall back via redirect.
• Old /provider-proxy endpoints are either removed or 301-redirected to avoid breaking old links.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 59a48f5 and ff84d35.

📒 Files selected for processing (1)
  • apps/deploy-web/env/.env (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ygrishajev
PR: akash-network/console#1461
File: apps/notifications/src/modules/alert/services/deployment-alert/deployment-alert.service.ts:194-197
Timestamp: 2025-06-10T14:19:14.122Z
Learning: The alert.CONSOLE_WEB_URL environment variable in the notifications app is controlled and configured by the Akash team, reducing XSS concerns for HTML link generation in alert messages.
apps/deploy-web/env/.env (2)
Learnt from: ygrishajev
PR: akash-network/console#1461
File: apps/notifications/src/modules/alert/services/deployment-alert/deployment-alert.service.ts:194-197
Timestamp: 2025-06-10T14:19:14.122Z
Learning: The alert.CONSOLE_WEB_URL environment variable in the notifications app is controlled and configured by the Akash team, reducing XSS concerns for HTML link generation in alert messages.
Learnt from: stalniy
PR: akash-network/console#1353
File: apps/deploy-web/src/config/browser-env.config.ts:0-0
Timestamp: 2025-05-22T14:25:01.336Z
Learning: For the `__AK_INJECTED_CONFIG__` global window property in the Akash Network Console, security is handled through cryptographic signature verification using a public key rather than property protection mechanisms like Object.defineProperty.
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: validate / validate-app
  • GitHub Check: test-build

@codecov
Copy link

codecov bot commented Jul 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.96%. Comparing base (59a48f5) to head (a151675).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1604   +/-   ##
=======================================
  Coverage   41.96%   41.96%           
=======================================
  Files         876      876           
  Lines       21339    21339           
  Branches     3874     3874           
=======================================
  Hits         8954     8954           
  Misses      12202    12202           
  Partials      183      183           
Flag Coverage Δ *Carryforward flag
api 74.82% <ø> (ø) Carriedforward from 09755d6
deploy-web 19.27% <ø> (ø)
notifications 87.90% <ø> (ø) Carriedforward from 09755d6
provider-proxy 82.13% <ø> (ø) Carriedforward from 09755d6

*This pull request uses carry forward flags. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ff84d35 and ce6deeb.

📒 Files selected for processing (1)
  • apps/deploy-web/env/.env.production (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ygrishajev
PR: akash-network/console#1461
File: apps/notifications/src/modules/alert/services/deployment-alert/deployment-alert.service.ts:194-197
Timestamp: 2025-06-10T14:19:14.122Z
Learning: The alert.CONSOLE_WEB_URL environment variable in the notifications app is controlled and configured by the Akash team, reducing XSS concerns for HTML link generation in alert messages.
Learnt from: stalniy
PR: akash-network/console#1353
File: apps/deploy-web/src/config/browser-env.config.ts:0-0
Timestamp: 2025-05-22T14:25:01.336Z
Learning: For the `__AK_INJECTED_CONFIG__` global window property in the Akash Network Console, security is handled through cryptographic signature verification using a public key rather than property protection mechanisms like Object.defineProperty.
apps/deploy-web/env/.env.production (1)
Learnt from: ygrishajev
PR: akash-network/console#1461
File: apps/notifications/src/modules/alert/services/deployment-alert/deployment-alert.service.ts:194-197
Timestamp: 2025-06-10T14:19:14.122Z
Learning: The alert.CONSOLE_WEB_URL environment variable in the notifications app is controlled and configured by the Akash team, reducing XSS concerns for HTML link generation in alert messages.
🪛 Gitleaks (8.26.0)
apps/deploy-web/env/.env.production

50-50: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: validate / validate-app
  • GitHub Check: test-build
  • GitHub Check: validate (apps/deploy-web) / validate-unsafe
🔇 Additional comments (1)
apps/deploy-web/env/.env.production (1)

50-50: Gitleaks flagged the Stripe publishable key—verify but likely safe.

Line 50 was reported as a “Generic API Key”. Stripe publishable keys are intentionally public and safe to embed in client bundles, so this is usually a false positive. Still, ensure it is the publishable (pk_live/ pk_test) key and not a secret key (sk_live/ sk_test) before dismissing the warning.

@baktun14 baktun14 merged commit af9aa70 into main Jul 1, 2025
57 checks passed
@baktun14 baktun14 deleted the fix/provider-proxy-url branch July 1, 2025 16:39
stalniy pushed a commit that referenced this pull request Nov 20, 2025
* fix(config): replace proxy url

* fix(auth): provider proxy url

* fix(auth): staging provider proxy urls

* fix(auth): remove values from the .env file
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.

2 participants

Comments