Repository navigation
docs(feature-flags): add the Feature Flags documentation page - #5962
Merged
Merged
Conversation
Document local rules, Agent variants, result validation, failure handling, and testing. Refs #5908
EnvelopeOptions, EvaluateSchemaResult, and the Variant evaluation option and result types appear in public signatures but had no export, so the API reference could not include them and callers could not import them.
…nt flags The Lambda extension and the standalone Agent container use different version numbers. Version 2.0.230173 is the standalone container build used to verify the RFC, so stating it as the minimum excluded every published Lambda extension layer, whose latest release is 2.0.27899. State the Lambda extension release that added multi-variant flags instead. Refs #5909
svozza
reviewed
Nov 16, 2026
svozza
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replace the Feature Flags documentation stub with the full utility page, so developers can go from installation to an evaluated flag and understand how the utility relates to Powertools for Python and to AppConfig multi-variant flags. Also complete the package README and API reference setup. Part of RFC discussion #5614 and #3754.
Changes
docs/features/feature-flags.md, structured like the Signer and Parameters pages:enabled;MODULO_RANGE;examples/snippets/feature-flags/: 25 includes, with new snippets, Flag Document JSON fixtures, and test examples. They follow the snippet conventions inCODING_STANDARDS.md.packages/feature-flags/typedoc.json, with one entry point per public sub-path, as the other packages do.EnvelopeOptions,EvaluateSchemaResult,EvaluateVariantOptions,EvaluateManyVariantOptions, andEvaluateManyVariantResultfrom the types entry point. They appear in public signatures but had no export, so callers couldn't import them and TypeDoc couldn't document them.AppConfigStoreOptionsandAppConfigAgentStoreOptionswith@expand, so their fields render inline on the store function pages.mkdocs build --strictstill fails on two existing generated-navigation warnings (api/and./llms.txt), not on this page. The non-strict build passes, and markdownlint, snippet lint, and snippet type-checks pass.Issue number: closes #5908
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.