sentry-options
AGENTS.md5 starsChanged 5 months agoApache-2.0View on GitHub
Sentry's internal option and feature-flag platform: schema-defined options, git-managed values, read at runtime. Values are validated, hot-reloadable, and backed by Kubernetes ConfigMaps. This repo holds the Rust and Python clients, the shared validation crate, sentry-options-cli, the sentry-options-gen-stubs pre-commit hook, and the reusable validate-schema workflow.
Files
sentry-options
Sentry's internal option and feature-flag platform: schema-defined options, git-managed values, read at runtime. Values are validated, hot-reloadable, and backed by Kubernetes ConfigMaps. This repo holds the Rust and Python clients, the shared validation crate, sentry-options-cli, the sentry-options-gen-stubs pre-commit hook, and the reusable validate-schema workflow.
Commands
- Rust format check:
cargo fmt --all -- --check - Rust lint:
cargo clippy --workspace --all-features --tests -- -D clippy::all - Rust tests:
SENTRY_OPTIONS_DIR=$PWD/sentry-options cargo test(.envrcsets the variable) - Python client tests, from
clients/python:uv sync --extra dev && uv run maturin develop && uv run pytest tests - Stub generator tests, from the repo root:
uv sync && uv run pytest - Pre-commit hooks:
pre-commit run --files <files>
Invariants
- Build the Python bindings (
clients/python) with maturin, nevercargo build. They are left out of the workspacedefault-membersfor this reason. - Schema changes must follow the evolution rules in docs/architecture.md. The
validate-schemaworkflow enforces them. CHANGELOG.mdis generated by craft at release (changelogPolicy: autoin.craft.yml).scripts/bump-version.shsets the versions.
Documentation
- README: what it is and a code quickstart
- docs/setup.md: integrating sentry-options into a new repo
- docs/options.md: adding and deleting options, setting values, testing
- docs/architecture.md: schema format, runtime model, feature-flag evaluation, CLI output, the injector
- examples/README.md: deploying the example image to a cluster
- examples/minikube_propagation/README.md: measuring ConfigMap propagation latency locally
In this repository2 other files it gives its agents.
- add-optionSkill
- onboardSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

