Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

spotify/confidence-resolver

Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

319 Commits
319 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Confidence Rust Flags Resolver

Status: Experimental

The Confidence flag resolver implemented in Rust, local-resolve OpenFeature Providers and edge-compatible resolver runnables.

Repository layout

The tools and SDKs published for direct usage:

Underlying building blocks:

  • confidence-resolver: Core resolver crate
  • wasm and wasm-msg: WASM resolver with communication contract towards the hosting environment
  • data: Sample local development data (e.g., resolver state)

Development - Quick Start

# With Docker (reproducible, no setup needed)
docker build .                    # Build, test, lint everything

Without docker, the building is managed via Makefile:

make                              # Same, using Makefile

# E2E tests require Confidence credentials passed as Docker secret
# Create openfeature-provider/js/.env.test with your credentials, then:
docker build \
  --secret id=js_e2e_test_env,src=openfeature-provider/js/.env.test \
  .

# With local tools (fast iteration)
make test                         # Run tests
make lint                         # Run linting
make build                        # Build WASM

# Build the Cloudflare-compatible resolver (WASM):
make cloudflare

Benchmarks

Small local benchmarks exist for Go and Node.js to validate end-to-end wiring. They are a work-in-progress and do not produce meaningful or representative performance numbers yet.

Run with Docker (streams all logs, cleans up containers afterward):

# Go benchmark
make go-bench

# Node.js benchmark
make js-bench

Notes:

  • Each target starts a dedicated mock server container and a one-shot bench container, then tears everything down.
  • Use docker compose up ... go-bench or ... js-bench to run them individually without Make.

License

See LICENSE for details.

About

Flag Resolvers for Confidence

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Morty Proxy This is a proxified and sanitized view of the page, visit original site.