Add TRIGGER_STREAMS_URL to auto-populated dev env vars

[ericallam]

Summary by CodeRabbit

• New Features

  • Introduced new environment variables: TRIGGER_API_URL, TRIGGER_STREAM_URL, TRIGGER_SECRET_KEY, and TRIGGER_RUNTIME_WAIT_THRESHOLD_IN_MS for both development and production environments.

• Bug Fixes

  • Enhanced error handling for creating, editing, and deleting environment variables to ensure accurate project and environment checks.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b97e9ec

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve modifications to the EnvironmentVariablesRepository class within the environmentVariablesRepository.server.ts file. New environment variables, specifically TRIGGER_API_URL and TRIGGER_STREAM_URL, have been added to the resolution functions for both development and production environments. The existing logic for creating, editing, and deleting environment variables remains unchanged, while error handling continues to ensure the integrity of project and environment checks. The methods responsible for fetching environment variables will now include these newly added variables.

Changes

File Path

Change Summary

apps/webapp/app/v3/environmentVariables/...

- Added TRIGGER_API_URL and TRIGGER_STREAM_URL to resolveBuiltInDevVariables and resolveBuiltInProdVariables. - Updated method signatures for resolveVariablesForEnvironment, resolveBuiltInDevVariables, and resolveBuiltInProdVariables (no parameter or return type changes). - Error handling in create, edit, delete, and deleteValue methods remains unchanged. - getEnvironment and getEnvironmentVariables methods will now include the new variables.

Possibly related PRs

• Fix updating many environment variables at once #1413: This PR modifies the create method within the same EnvironmentVariablesRepository class in the environmentVariablesRepository.server.ts file, which is directly related to the management of environment variables, similar to the changes made in the main PR.

Suggested reviewers

• nicktrn

Poem

In the burrow deep, where the secrets lie,
New variables sprout, reaching for the sky.
TRIGGER_API_URL, TRIGGER_STREAM too,
In the world of code, they hop into view.
With a twitch of my nose, I celebrate this feat,
For every new change makes our project sweet! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/webapp/app/v3/environmentVariables/environmentVariablesRepository.server.ts

(node:42930) ESLintIgnoreWarning: The ".eslintignore" file is no longer supported. Switch to using the "ignores" property in "eslint.config.js": https://eslint.org/docs/latest/use/configure/migration-guide#ignoring-files
(Use node --trace-warnings ... to show where the warning was created)

Oops! Something went wrong! :(

ESLint: 9.15.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

---

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

[pkg-pr-new]

@trigger.dev/react-hooks

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/react-hooks@1485

@trigger.dev/rsc

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/rsc@1485

@trigger.dev/core

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1485

@trigger.dev/sdk

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1485

@trigger.dev/build

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1485

trigger.dev

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev@1485

commit: b97e9ec