docs(plan): GraphQL-based pgpm export feature plan#745
Open
pyramation wants to merge 1 commit intomainfrom
Open
docs(plan): GraphQL-based pgpm export feature plan#745pyramation wants to merge 1 commit intomainfrom
pyramation wants to merge 1 commit intomainfrom
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.
docs(plan): add GraphQL-based pgpm export feature plan
Summary
Adds a planning document at
docs/plan/graphql-export.mdthat describes how to makepgpm exportwork over GraphQL instead of direct SQL, so customers without database access can export their schema metadata via their GraphQL API endpoint.The plan covers:
pg_catalog,db_migrate.sql_actions,information_schema)ExportDataSourceabstraction pattern with SQL and GraphQL implementationsdb_migrate.sql_actionsblocker (not exposed via GraphQL) with mitigation optionsNo code changes — this is a planning document only.
Review & Testing Checklist for Human
db_migrate.sql_actionsblocker assessment. The plan recommends metadata-only export as Phase 1 and defers migration SQL export. Confirm this scoping is acceptable or ifsql_actionsmust be exposed via GraphQL from the start.ExportDataSourceabstraction is the right pattern. The plan proposes an interface with SQL/GraphQL implementations. Validate this aligns with the team's preferred architecture.InflektPresetcustomizes naming. Verify the example mappings (e.g.allSchemas,allFields) match the actual server schema.Notes