feat(export): add integration_providers_module to meta export#1361
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
Adds
metaschema_modules_public.integration_providers_moduleto the@pgpmjs/exportmeta export path, upstreaming the localpatches/@pgpmjs+export@0.26.4.patchused in constructive-db (so that patch can be dropped once this is released).Changes (all in
pgpm/export):META_TABLE_ORDER+META_TABLE_CONFIG: newintegration_providers_moduleentry, placed afteridentity_providers_moduleexportMeta(SQL flow):SELECT * FROM metaschema_modules_public.integration_providers_module WHERE database_id = $1 ORDER BY idexportGraphQLMeta(GraphQL flow): correspondingqueryAndParse('integration_providers_module')Fields are discovered dynamically at export time, so no per-field config is needed; on databases where the table doesn't exist yet, the exporter skips it silently (existing 42P01 / introspection-miss behavior).
pnpm testinpgpm/export: 142/142 pass.Link to Devin session: https://app.devin.ai/sessions/fa0bd53e497742d2ab69753d3a7b3f4c
Requested by: @pyramation