Repository navigation
Report plugin activation in /info at request time, not at startup - #2577
Merged
Merged
Conversation
This was referenced Nov 3, 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.
/inforeportedconfiguration.plugins.<id>Enabledfrom a snapshot taken at startup, in two places:PluginsConfigurationInfocalledplugin.isActive()once, in its constructor.InfoServicebuilt the wholeInfoobject once, in its own constructor.A plugin that only becomes active after those beans are created could be reported as disabled until the next restart, and a plugin that stops later stayed reported as enabled. TrexSQL is one example: it is active once its engine has started. Atlas 3 is moving to this flag to decide whether to show the cache UI (OHDSI/Atlas3#472).
Both values are now worked out on each request. Added unit tests for both classes.