Deploy preview for hasura-docs ready!

Built with commit 0596a44

https://deploy-preview-1876--hasura-docs.netlify.com

Review app for commit 56551e9 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-56551e9

Review app for commit 2e68cb3 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-2e68cb3

./hasura-dev metadata track --table table_1 --table table_2 --all-relationships

The issue is table_2 has a foreign key to table_3 and the command is trying to track that too.

This issue is there on console too tracked in #1882

2. Trying to track the already tracked table responds with a success message.

➜ ./hasura-dev metadata track --table table_1 --table table_2

@arvi3411301 @shahidhk

3. ./hasura-dev metadata untrack --table table1

INFO untrack command executed successfully

table1 doesn't exist. Should it say that?

@shahidhk What should we do in this case? Track only the relationships with the reference table name matches the --table flag?

@karthikvt26 Is the relationships name generated is according to the console?

@arvi3411301 Yes

1. We should only track relations across the tables and schema that are being tracked.
2. Trying to track a table that is already tracked should succeed, but with a message saying the table is already tracked.
3. Tracking a table that doesn't exist should fail.

Also, while tracking all tables relations etc, the logs should clearly output what is tracked.

Review app for commit 4027118 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-4027118

Trying to track a table that is already tracked should succeed, but with a message saying the table is already tracked.

Will this also work for the track metadata API. Currently on SQL page if the checkbox is tracked and the table is already tracked the entire operation fails

Review app for commit 81852c8 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-81852c8

@karthikvt26 I had fixed column conflicts. Can you try again if this build fixes all issues?

Review app for commit de663c8 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-de663c8

Review app for commit 474ab73 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-474ab73

@arvi3411301 Running with --table and --all-relationship option is not tracking the relationships

➜  my-project ./hasura-dev metadata track --table table_1  --all-relationships
ERRO auto-update failed, run 'hasura update-cli' to update manually  error="cannot update from a non-semver version: pull1876-474ab73"
INFO tables/relationships tracked successfully    
➜  my-project ./hasura-dev metadata track --table table_2  --all-relationships
ERRO auto-update failed, run 'hasura update-cli' to update manually  error="cannot update from a non-semver version: pull1876-474ab73"
INFO tables/relationships tracked successfully    

@karthikvt26 In order to track relationships across tables, you need to specify --table table2.

So, the command will be

hasura metadata track --table table1 --table table2 --all-relationships

Ok the message is slightly confusing then (table/relationships tracked successfully)

@karthikvt26 We will be adding info/warn messages if something is missing.

Something like,

WARN: relationship referencing to table2 (cols) from table1 (cols) cannot be created since --table table2 is missing from command.

But at the end, table/relationships tracked successfully will be displayed to the user if there are metadata actions present in the bulk query.

@arvi3411301 No no can we add logs as

1. INFO tables tracked successfully
2. INFO relationships tracked successfully (will not be there if no relationships are tracked)

@shahidhk

Review app for commit 85265d3 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-85265d3

Review app for commit 6fe34aa deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-6fe34aa

Review app for commit 0596a44 deployed to Heroku: https://hge-ci-pull-1876.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1876-0596a44

Review app https://hge-ci-pull-1876.herokuapp.com is deleted

@arvi3411301 Why was this closed?

@shahidhk need to rewrite everything. Will open a new PR.