hasura / hasura/graphql-engine

Need automation support to apply across multiple metadata scripts

Open
#7,155 2 comments 0 reactions 0 assignees View on GitHub
c/cli c/v3-cli k/enhancement s/triaged v2 v3
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

Hasura team,

Will describe below the scenario, problem statement and the request

**Scenario**: We have multiple products. Each product is managed and maintained by different teams in independent repos and in unique PG schemas. We also have certain common models that will be required by all products. Our customers usually need more than 1 product at a time. This will imply multiple migration and metadata scripts will need to be run on the same gql engine and pg instance. We cannot expect for all products to be maintained in the same schema and repo.

**Problem statement**: Lets say there are metadata scripts for 2 different schemas Schema1 and Schema2. Let execute migration and metadata scripts for Schema1. Now lets run the migration and metadata for Schema2. All metadata for Schema1 is lost
Request: Ask is to:

1. Pl ensure metadata is not overwritten for Schema(n-x). And all individual metadata are applied.
2. OR Provide a tool to merge multiple metadata yawls/scripts. So once all migrations are executed we can run 1 integrated metadata. Intention is to integrate this with the CD pipeline

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.