quonfig 0.0.19 → 0.0.21

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f71f10c80365079815e7b7d7f2a9a8926ecfc358697505bb3c6bd3f2e6142976
-  data.tar.gz: 3d0988da2eb9a17457dc53c358e32a55aaa17f59e1c7c280db5db52b3eb991fc
+  metadata.gz: 417fb2012b91e48124294300c5d480ef08a822a6f5c42efff05e9334336ae884
+  data.tar.gz: a5fe1a4548e4d332ada2ce2c01c4d74f604d1273ad8d58338d3ea8653670629c
 SHA512:
-  metadata.gz: e019ac9393b2644208aaa79fbbed9bfe0a27e346413ffac2cd126d47fd9ffa114a1af4bfcd597b527577935a586ea6636aa6e8c96be8ee657889bc324d9ea38c
-  data.tar.gz: 89026759a78f4219766b14366630a5df3a3126884c5bfa721764cffdf6799c8f47df5be1245c86c8966aedbbb9a4508b65d53a400cd3c6e4308f872bc975f6ce
+  metadata.gz: aa3cd21079aad1feb9b7ddab61dacb4e9ebb79dcf1562b2283b46b50daa613fe844f9685015bd3f82efd3200817b8ba032899ce0a7a785a3fcfeda994417daf3
+  data.tar.gz: 0d848cebe378a700f9accd09cdbe6dcd78071a83a9c56734fa765e094b36acadf5f888d46fbb7dbc81c76e06a0611ac68dc1a2689833aef08f57e2674cfe8c71

data/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.0.21 - 2026-06-02
+
+- **Dev-context injection is now default-on (qfg-bw7g.5).** `enable_quonfig_user_context` now defaults to `nil` (unset). When left unset it defaults to **on**, gated solely by the presence of `~/.quonfig/tokens.json`; the loader no-ops without that file, so this stays inert in production. New `dev_context_enabled?` precedence: explicit `enable_quonfig_user_context` option ?? `QUONFIG_DEV_CONTEXT` env (`true`/`false`) ?? `true`. Pass `enable_quonfig_user_context: false` or set `QUONFIG_DEV_CONTEXT=false` to opt out.
+
+## 0.0.20 - 2026-05-29
+
+- **Fix (delivery): derive evaluator env from `meta.environment` in HTTP+SSE delivery mode (qfg-xpln.2).** Per-environment overrides were not being applied when the SDK ran in delivery mode (HTTP fetch + SSE stream). The evaluator now derives its `env_id` from the authoritative `meta.environment` carried on every delivery envelope, so environment-scoped rules and overrides resolve correctly against the environment api-delivery actually served — matching datadir-mode behavior.
+- **Fix (options): an explicit environment pin is datadir-only; ignored in delivery mode with a WARN (qfg-pinh).** In delivery mode the served envelope's `meta.environment` is authoritative — the environment is decided server-side by api-delivery, not by the client. A client-supplied environment pin (`with_environment` / `QUONFIG_ENVIRONMENT`) is therefore only meaningful in datadir mode. In delivery mode the pin is now ignored and a one-time WARN is logged so the conflict is visible rather than silently misleading.
+
 ## 0.0.19 - 2026-05-28
 
 - **Deprecation (context): `in_context` is now a deprecated alias of `with_context` (qfg-e0kk).** The two methods have always been runtime-identical — both accept a properties hash and either yield a `Quonfig::BoundClient` to a given block or return the BoundClient directly. As part of the sdk-1.0 unification, every SDK in the family is converging on the `with_context` family; sdk-ruby keeps `in_context` as a YARD-`@deprecated` alias for the 1.0.0 cycle so existing customer code (especially Prefab-fork lineage call sites) keeps working without a runtime warning. Implementation collapses to a one-line forward (`in_context` now calls `with_context`), and the README example is updated to use `with_context`. Slated for removal in 2.0.0.

data/lib/quonfig/client.rb

@@ -714,6 +714,14 @@ module Quonfig
       old_keys = @store.keys.to_set
       (old_keys - new_keys).each { |k| @store.delete(k) }
       envelope.configs.each { |cfg| @store.set(cfg['key'], cfg) }
+      # qfg-pinh: evaluate against the installed envelope's meta.environment,
+      # matching sdk-go. In datadir mode the loader stamps meta.environment =
+      # the resolved env (the `environment:` pin or QUONFIG_ENVIRONMENT), so
+      # this also covers the env-var-only case where @options.environment is
+      # nil at evaluator construction.
+      meta = envelope.respond_to?(:meta) ? envelope.meta : nil
+      env_id = meta && (meta['environment'] || meta[:environment])
+      @evaluator.env_id = env_id if env_id && !env_id.to_s.empty?
       record_refresh!
     end
 
@@ -761,6 +769,8 @@ module Quonfig
     def initialize_network_mode
       raise Quonfig::Errors::InvalidSdkKeyError, @options.sdk_key if @options.sdk_key.nil? || @options.sdk_key.to_s.strip.empty?
 
+      warn_if_pin_ignored_in_delivery_mode
+
       @config_loader = Quonfig::ConfigLoader.new(@store, @options)
 
       perform_initial_fetch
@@ -791,10 +801,52 @@ module Quonfig
       if result == :failed
         handle_init_failure(RuntimeError.new('Config fetch failed against all api_urls'))
       else
+        sync_evaluator_env_id!
         record_refresh!
       end
     end
 
+    # qfg-pinh: In SDK-key DELIVERY mode the server's `meta.environment` is
+    # AUTHORITATIVE. The server scopes each config to a single environment and
+    # reports the active env id in `meta.environment` (the loader captures it
+    # as @config_loader.environment_id). The evaluator must always evaluate
+    # against that installed env id — matching sdk-go, where eval never
+    # branches on the pin (c.envID = envelope.Meta.Environment, quonfig.go:850).
+    #
+    # An explicit environment pin (`environment:` option / QUONFIG_ENVIRONMENT)
+    # is DATADIR-ONLY: in delivery mode it is IGNORED (it only feeds the datadir
+    # loader, which stamps meta.environment = pin). So we always adopt the
+    # server's env id here regardless of the pin. A WARN is emitted once at init
+    # (see #warn_if_pin_ignored_in_delivery_mode) when a pin is set in delivery
+    # mode so customers aren't surprised that it has no effect.
+    #
+    # qfg-xpln.2 originally only adopted the server env when NO pin was set,
+    # which let the pin win in delivery mode — qfg-pinh reverses that.
+    def sync_evaluator_env_id!
+      return unless @config_loader.respond_to?(:environment_id)
+
+      server_env = @config_loader.environment_id
+      @evaluator.env_id = server_env if server_env && !server_env.to_s.empty?
+    end
+
+    # qfg-pinh: an explicit environment pin (`environment:` option or
+    # QUONFIG_ENVIRONMENT) is DATADIR-ONLY. In delivery (SDK-key) mode the
+    # active environment is determined by the SDK key and reported via
+    # `meta.environment`, so the pin is ignored. Warn once at init so the
+    # customer isn't surprised the setting has no effect. Fired only on the
+    # delivery-mode init path (datadir mode honors the pin and never calls
+    # this).
+    def warn_if_pin_ignored_in_delivery_mode
+      env = @options.environment
+      return if env.nil? || env.to_s.empty?
+
+      LOG.warn(
+        "[quonfig] environment '#{env}' was set but the client is in delivery " \
+        '(SDK-key) mode; the active environment is determined by the SDK key, ' \
+        'so this setting is ignored (it applies only when loading from a local data dir)'
+      )
+    end
+
     def handle_init_failure(err)
       if @options.on_init_failure == Quonfig::Options::ON_INITIALIZATION_FAILURE::RETURN
         LOG.warn "[quonfig] Initialization did not complete cleanly; continuing with empty store: #{err.message}"
@@ -821,6 +873,7 @@ module Quonfig
 
         begin
           @config_loader.apply_envelope(envelope)
+          sync_evaluator_env_id!
           handle_sse_state_change(:connected)
           record_refresh!
         rescue StandardError => e
@@ -858,6 +911,7 @@ module Quonfig
           break if stopped_ref.call
 
           @config_loader.fetch!
+          sync_evaluator_env_id!
           record_refresh!
           notify_delivered.call
           notify_on_update_callback
@@ -899,9 +953,7 @@ module Quonfig
     # customer's so any explicit `quonfig-user` keys win on collision.
     def build_initial_global_context(options)
       customer = normalize_context(options.global_context)
-      enabled = options.enable_quonfig_user_context == true ||
-                ENV['QUONFIG_DEV_CONTEXT'] == 'true'
-      return customer unless enabled
+      return customer unless dev_context_enabled?(options)
 
       dev = Quonfig::DevContext.load_quonfig_user_context
       return customer if dev.nil?
@@ -909,6 +961,21 @@ module Quonfig
       merge_contexts(dev, customer)
     end
 
+    # Tri-state resolution for dev-context injection. Default ON, gated only
+    # by the presence of the tokens file (the loader no-ops without it ->
+    # dead in prod). Precedence: an explicit option (non-nil) wins, else
+    # QUONFIG_DEV_CONTEXT ('true'/'false'), else true.
+    def dev_context_enabled?(options)
+      opt = options.enable_quonfig_user_context
+      return opt == true unless opt.nil?
+
+      case ENV.fetch('QUONFIG_DEV_CONTEXT', nil)
+      when 'true' then true
+      when 'false' then false
+      else true
+      end
+    end
+
     def normalize_context(ctx)
       return {} if ctx.nil?
       return ctx if ctx.is_a?(Hash)

data/lib/quonfig/options.rb

@@ -194,7 +194,9 @@ module Quonfig
       global_context: {},
       logger_key: nil,
       logger: nil,
-      enable_quonfig_user_context: false,
+      # Tri-state (nil = unset). Default ON, gated only by the presence of
+      # ~/.quonfig/tokens.json; see Client#build_initial_global_context.
+      enable_quonfig_user_context: nil,
       data_dir_auto_reload: false,
       data_dir_auto_reload_debounce_ms: 200
     )

data/lib/quonfig/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Quonfig
-  VERSION = '0.0.19'
+  VERSION = '0.0.21'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: quonfig
 version: !ruby/object:Gem::Version
-  version: 0.0.19
+  version: 0.0.21
 platform: ruby
 authors:
 - Jeff Dwyer
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-05-28 00:00:00.000000000 Z
+date: 2026-06-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport