open-feature / open-feature/spec
Consider the ability to opt-out from automatic functionality such as automatic provider ready events.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 58
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 2
Description
For providers which support changing their provider status at runtime the automatic events introduce additional complexity.
The provider needs to defer its handling of the status until after the automatic status provided by the OpenFeature API. Otherwise it would emit duplicate provider ready or error events. The handling can be somewhat complex for multi-threaded providers and SDKs.
It would be nice if the provider had meta-data, or other fields, which could allow for opting out of the automatic behavior. This may then be extended to other automatic functionality in the future.
Related discussion: https://github.com/open-feature/dotnet-sdk/pull/276#issuecomment-2163766166
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the issue body and the linked discussion on open-feature/dotnet-sdk#276. Clarify the provider metadata or field needed to opt out of automatic ready and error events, including how it interacts with runtime status changes and multithreaded providers. Done means the specification defines the opt-out behavior and its event semantics.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100