prefab-cloud-ruby

Ruby Client for Prefab FeatureFlags, Config as a Service: https://www.prefab.cloud

client = Prefab::Client.new

lookup_key = "user-123"
identity_attributes = {
  team_id: 432,
  user_id: 123,
  subscription_level: 'pro',
  email: "[email protected]"
}

result = client.enabled? "my-first-feature-flag", lookup_key, identity_attributes

puts "my-first-feature-flag is: #{result} for #{lookup_key}"

See full documentation https://docs.prefab.cloud/docs/ruby-sdk/ruby

Supports

FeatureFlags as a Service
Millions of individual limits sharing the same policies
WebUI for tweaking limits & feature flags
Infinite retention for deduplication workflows

Important note about Forking and realtime updates

Many ruby web servers fork. GRPC does not like to be forked. You should manually start gRPC streaming in the on_worker_boot or after_fork hook of your server. See some details on GRPC and forking: https://github.com/grpc/grpc/issues/7951#issuecomment-335998583


#config/initializers/prefab.rb
$prefab = Prefab::Client.new
Rails.logger = $prefab.log

#puma.rb
on_worker_boot do
  $prefab.config_client.start_streaming
end

Logging & Debugging

In classpath or ~/.prefab.default.config.yaml set

log-level:
  cloud.prefab: debug

To debug issues before this config file has been read, set env var

PREFAB_LOG_CLIENT_BOOTSTRAP_LOG_LEVEL=debug

Contributing to prefab-cloud-ruby

Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
Fork the project.
Start a feature/bugfix branch.
Commit and push until you are happy with your contribution.
Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Release