hasura / hasura/graphql-engine

Metadata apply CLI needs an import/incremental strategy

Open
#7,920 0 comments 1 reaction 0 assignees View on GitHub
c/cli k/enhancement t/product-platform
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Is your proposal related to a problem?

metadata apply currently replaces existing metadata. In the future, I can imagine a case where users will want to consume multiple existing patterns from other projects with a flow similar to `metadata apply action from existing-project`.

### Describe the solution you'd like

The ability to:
1. Define which project I want to apply metadata from
2. Define the path to which type of metadata I want to apply from that project (perhaps even which named item in that metadata)
3. Define the merge strategy (replace, add, merge) for the metadata getting applied
-- Nice to have ---
4. Ideally, define a remote source for the metadata from location.
5. If it was technically possible, define a remote source for the "to" location. Ie, apply Github sourced metadata to my Cloud repo via CLI. Allows for agencies to define custom features not privy to public consumption.

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.