ref(options): migrate runtime config to sentry-options (Python RPC/query + Rust killswitches)

[phacops]

What

Migrates a batch of Redis-backed runtime config keys to sentry-options, and wires up the Python sentry-options client so Python code can read the same snuba namespace the Rust consumers already use (via the sentry-options crate, e.g. blq_router.rs). Values stay managed centrally in sentry-options-automator; Snuba reads them read-only.

Three commits:

1. Introduce the Python client + migrate enable_any_attribute_filter.
2. Migrate 12 more read-only Python RPC/query keys.
3. Migrate 2 static Rust consumer killswitches.

Infrastructure

• Dependency: sentry-options>=1.1.1 (pyproject.toml, uv.lock) — the Python binding of the same client the Rust consumers use.
• Wrapper snuba/state/sentry_options.py:
  • init_options() — idempotent, never raises (a missing/misconfigured options mount must not break startup); called from setup_sentry(), the chokepoint every entrypoint and pytest_configure already hits.
  • get_option(key, default) and typed get_bool_option / get_int_option / get_float_option / get_str_option(key, default) — return the configured value (or schema default), falling back to the caller's default on any OptionsError. Mirrors the Rust .ok()...unwrap_or(default) semantics so call sites behave exactly as before.
• conftest.py points SENTRY_OPTIONS_DIR at the in-repo schema so init() is cwd-independent.

Keys migrated

Python (RPC / query path) — schema type / default match the prior get_*_config default, so behavior is unchanged until a value is set in automator:

key	type	default
enable_any_attribute_filter	boolean	true
aggregation_deprecation_enabled	boolean	true
enable_trace_pagination	boolean	true
use.low.cardinality.processor	boolean	true
cross_item_queries_no_sample_outer	boolean	true
default_tier	integer	1
export_trace_items_default_page_size	integer	10000
use_sampling_factor_timestamp_seconds	integer	1744131600
ExecutionStage.max_query_size_bytes	integer	131072
EndpointGetTrace.apply_final_rollout_percentage	number	0.0
rpc_logging_sample_rate	number	0.0
rpc_logging_flush_logs	number	0.0
ExecutionStage.disable_max_query_size_check_for_clusters	string	""

Rust consumers (previously read via runtime_config::get_str_config, i.e. a PyO3 round-trip into Python/Redis — now read natively, no PyO3):

key	type	default
eap_items_drop_invalid_timestamps	boolean	false
experimental_healthcheck	boolean	false

Tests that toggled these via state.set_config(...) / patch_str_config_for_test(...) now use sentry_options.testing.override_options(...) (Python) / sentry_options::testing::override_options(...) (Rust).

Deliberately NOT migrated

sentry-options requires every key to be declared in a static schema, so dynamically-named / parameterized keys can't move, and the runtime-config management plane must stay:

• Dynamic / parameterized keys (Python & Rust): per-storage / per-policy / per-topic / per-consumer-group keys — e.g. clickhouse_load_balancing:<storage>, clickhouse_max_insert_block_size:<storage>, eap_items_dlq_grace_period_min:<storage>, quantized_rebalance_consumer_group_delay_secs__<group>, validate_schema_<topic>, allocation-policy configs, rate-limiter buckets.
• The runtime-config management plane: the admin UI / CLI / snuba.state CRUD and audit log — sentry-options has no in-Snuba write path, and it manages the keys that can't migrate.
• List/JSON-valued and string-parsed keys (e.g. CSV allowlists/denylists, generic_metrics_use_case_killswitch) — these don't map cleanly to a scalar option and are left for a follow-up.
• enable_long_term_retention_downsampling — migratable, but its test refactor needs care; deferred to a follow-up.

Operational note

After cutover these keys are read-only from Snuba and edited in sentry-options-automator (not the admin UI). For each, set the value in automator to match any current production override before this lands; effective defaults are otherwise unchanged. Several are operational killswitches — flagging so reviewers can veto moving any specific one off the live admin toggle. Deploy-infra detail to confirm: the options ConfigMap is mounted for the Python web/RPC pods (the Rust consumer pods already have it).

Verification

• pytest tests/state/test_sentry_options.py → 6 passed; mypy (strict) clean on changed source; ruff check + ruff format --check clean.
• Rust: cargo check clean; cargo test healthcheck (2) + utils (4) pass. The runtime_config PyO3 tests fail only in this sandbox (no Python bootstrap) — they're unrelated to these changes and run in CI.
• The RPC/endpoint integration tests need ClickHouse and were not run locally; CI covers them.

🤖 Generated with Claude Code

---

Generated by Claude Code

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7659d7a. Configure here.}