[codex] add canonical connector plugin metadata#126
Open
soheil-oai wants to merge 1 commit intomainfrom
Open
Conversation
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
1 participant
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.
This adds explicit metadata for canonical connector-backed plugins so downstream consumers can resolve a definitive
connector_id -> pluginmapping.Today, the repo stores connector identity in each plugin's
.app.json, but it does not distinguish between a plugin that merely references a connector and the official base plugin for that connector. Because the plugin model allows multiple plugins to reference the same connector, a consumer that starts from connector IDs does not currently have a repo-native way to identify the canonical curated plugin.This change adds
canonical: truealongside the connector ID in the app manifests for the connector-backed curated plugins, and documents that convention in the README. Keeping the metadata in.app.jsonplaces the canonical marker next to the connector identity itself and avoids introducing a second source of truth elsewhere in the repo.The immediate effect is that systems which only have connector IDs can now perform a deterministic lookup of the canonical plugin without relying on naming conventions or ad hoc allowlists. The change is intentionally narrow and does not alter plugin loading behavior, marketplace policy, or connector wiring.
Validation was limited to parsing the edited
.app.jsonfiles and checking that the repo contains a single canonical entry per marked connector ID.