hasura / hasura/graphql-engine

Show applied migrations in CLI image (like hasura-cli does)

Open
#8,751 1 comment 4 reactions 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?

with debug log level, hasura-cli shows which migrations are applied. but the docker-cli image doesn't.

Here's `hasura-cli migrate apply --skip-update-check --project hasura --log-level DEBUG`

![image](https://user-images.githubusercontent.com/11539524/183079836-05e21051-6bbb-418e-b65d-6fe6a575faeb.png)

And here's the only information provided by `hasura/graphql-engine:v2.9.0.cli-migrations-v2` image with `HASURA_GRAPHQL_LOG_LEVEL: debug`

`{"timestamp":"2022-08-05T12:31:23.000+0000","level":"info","type":"startup","detail":{"kind":"migrations-apply","info":"applying migrations from /hasura/migrations"}}`

### Describe the solution you'd like

I would like the same debug lines to be present, one for each migration applied.

### Describe alternatives you've considered

There are none.

### If the feature is approved, would you be willing to submit a PR?

doubtful

Contributor guide

Open the contributing guide

Research direction

Start with the `hasura/graphql-engine:v2.9.0.cli-migrations-v2` startup path and compare its `HASURA_GRAPHQL_LOG_LEVEL=debug` output with `hasura-cli migrate apply --skip-update-check --project hasura --log-level DEBUG`. Done means the Docker CLI image emits one debug line for each applied migration.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.