Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Release #209

Merged
merged 1 commit into from
Feb 18, 2025
Merged

New Release #209

merged 1 commit into from
Feb 18, 2025

Conversation

evervault-dependencies
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@evervault/[email protected]

Minor Changes

  • 720476d: Extend Relay outbound/forward proxy support in Node to include the ability to filter requests by path using decryptionDomains.

    Requests can be filtered at the path level by appending an absolute or wildcard path to the decryption domains option, following similar wildcard logic to the domains
    themselves. For example:

    // Existing behaviour will be observed, proxying requests to the host 'api.com'.
    const ev = new Evervault('app_uuid', 'api_key', {
      decryptionDomains: ['api.com'],
    });
    
    // Will only proxy requests to host 'api.com' which have a path starting with '/users/'.
    const ev = new Evervault('app_uuid', 'api_key', {
      decryptionDomains: ['api.com/users/*'],
    });
    
    // Will only proxy requests to host 'api.com' which have an exact path of '/settings'.
    const ev = new Evervault('app_uuid', 'api_key', {
      decryptionDomains: ['api.com/settings'],
    });

    This change is compatible with the existing hostname wildcard behaviour of decryptionDomains.

@lfarrel6 lfarrel6 merged commit 8378a2b into master Feb 18, 2025
7 checks passed
@lfarrel6 lfarrel6 deleted the changeset-release/master branch February 18, 2025 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants