Skip to content

feat: add isolated instance#368

Merged
toddbaert merged 3 commits intomainfrom
feat/isolated-instance
Apr 8, 2026
Merged

feat: add isolated instance#368
toddbaert merged 3 commits intomainfrom
feat/isolated-instance

Conversation

@toddbaert
Copy link
Copy Markdown
Member

@toddbaert toddbaert requested a review from a team as a code owner February 26, 2026 12:31
@toddbaert toddbaert requested review from beeme1mr and justinabrahms and removed request for justinabrahms February 26, 2026 12:31
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @toddbaert, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the OpenFeature specification by introducing the concept of isolated API instances. This change addresses advanced use cases such as micro-frontends, dependency injection, and testing scenarios, where independent API instances with fully isolated state are required. It defines how these instances should be created, behave, and manage their associated providers, moving beyond the default global singleton model.

Highlights

  • Introduced Isolated API Instances: Added the concept of 'Isolated API Instances' to the OpenFeature specification, allowing for independent, non-singleton API instances with their own state.
  • Defined Glossary Term: Included 'Isolated API Instance' in the specification's glossary, providing a clear definition for this new concept.
  • Detailed Requirements for Isolated Instances: Added a new section (1.8) to the flag evaluation specification, outlining six requirements for isolated API instances, covering their creation, behavior, and provider management.
Changelog
  • specification/glossary.md
    • Added 'Isolated API Instance' to the table of contents.
    • Included a detailed definition for 'Isolated API Instance'.
  • specification/sections/01-flag-evaluation.md
    • Added a new section '1.8. Isolated API Instances' to the flag evaluation document.
    • Defined the need for isolated instances with examples like micro-frontends and testing.
    • Introduced Requirement 1.8.1 for a factory function to create independent API instances.
    • Specified Requirement 1.8.2 that isolated instances must conform to the same API contract.
    • Recommended in Requirement 1.8.3 that the factory function be housed in a distinct module for discoverability.
    • Stipulated in Requirement 1.8.4 that a provider instance must not be registered with more than one API instance simultaneously.
    • Required in Requirement 1.8.5 that the provider mutator must indicate an error if a provider is already bound.
    • Mandated in Requirement 1.8.6 that a provider must be unbound when no longer registered with an API instance.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces the concept of "Isolated API Instances" to the OpenFeature specification. It includes a new glossary entry and a detailed section outlining the requirements for creating and managing these independent API instances. The changes are well-documented, providing clear rationale, examples, and cross-references to other parts of the specification. The addition addresses advanced use cases such as micro-frontends and dependency injection, enhancing the flexibility of the OpenFeature API.

@toddbaert toddbaert force-pushed the feat/isolated-instance branch from d40726d to 85bb12b Compare February 26, 2026 12:33
@toddbaert toddbaert changed the title feat: add isolated instanc feat: add isolated instance Feb 26, 2026
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
@toddbaert toddbaert force-pushed the feat/isolated-instance branch from 85bb12b to d16ebc8 Compare February 26, 2026 12:34
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Copy link
Copy Markdown
Member

@lukas-reining lukas-reining left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me!

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
@toddbaert toddbaert force-pushed the feat/isolated-instance branch from ce29fb2 to d48f002 Compare March 3, 2026 16:15
@toddbaert toddbaert merged commit a5a2ba3 into main Apr 8, 2026
7 checks passed
@toddbaert toddbaert deleted the feat/isolated-instance branch April 8, 2026 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Considering alternatives to the OpenFeature global singleton

7 participants