Cannot Create Migration

Versions:

• Hasura GraphQL version: v1.0.0-beta.2 using docker

• CLI Version: v1.0.0-beta.2

• OS Windwos 10

Steps to reproduce:

• Set console to false

• Launch console with hasura.exe console worked and no errors or warning found.

• I’ve migrated several times before, using CLI with the command hasura.exe migrate create "migrate_name" --from-server and generated both .yaml and .sql file.

• I’ve tried migration again after some addition and changes it’s getting failed with reason:

cannot fetch schema dump: invalid character '<' looking for beginning of value

with the result only generated .yaml file. I don’t know what changes have caused this situation because there are too many additions and changes made and so far no errors have been found when the client making the request (query, mutation even sub). So I assume it’s work perfectly.

[hynra]

I solved this issue by running migration on the remote server and exclude caddy from docker-compose.yaml. We running Hasura on an existing database with a monolith architecture, we have like 80+ tables and thousands of data. When I run a manual migration, It’s like take sometimes that Caddy rules cannot handle that (timeout or something).

This is my docker-compose based on Hasura doc in previous version:

version: '3.6'
services:
  postgres:
    image: postgres:10.5
    restart: always
    volumes:
    - db_data:/var/lib/postgresql/data
  graphql-engine:
    image: hasura/graphql-engine:v1.0.0-beta.4
    depends_on:
    - "postgres"
    restart: always
    environment: 
      HASURA_GRAPHQL_DATABASE_URL: postgresql://postgres:blah
      # enable the console served by server
      HASURA_GRAPHQL_ENABLE_CONSOLE: "false" # set "false" to disable console
      ## uncomment next line to set an admin secret key
      # this is comment
      HASURA_GRAPHQL_ENABLE_TELEMETRY: "false"
      HASURA_GRAPHQL_ADMIN_SECRET: adminsecret
    command:
    - graphql-engine 
    - serve
  caddy:
    image: abiosoft/caddy:0.11.0
    depends_on:
    - "graphql-engine"
    restart: always
    ports:
    - "80:80"
    - "443:443"
    volumes:
    - ./Caddyfile:/etc/Caddyfile
    - caddy_certs:/root/.caddy
volumes:
  db_data:
  caddy_certs:

So, I updated with v1.0.0-beta.4 and realized that in Install Manifest there is no Caddy anymore

version: '3.6'
services:
  postgres:
    image: postgres
    restart: always
    volumes:
    - db_data:/var/lib/postgresql/data
  graphql-engine:
    image: hasura/graphql-engine:v1.0.0-beta.4
    ports:
    - "8080:8080"
    depends_on:
    - "postgres"
    restart: always
    environment:
      HASURA_GRAPHQL_DATABASE_URL: postgres://postgres:@postgres:5432/postgres
      HASURA_GRAPHQL_ENABLE_CONSOLE: "true" # set to "false" to disable console
      HASURA_GRAPHQL_ENABLED_LOG_TYPES: startup, http-log, webhook-log, websocket-log, query-log
      ## uncomment next line to set an admin secret
      # HASURA_GRAPHQL_ADMIN_SECRET: myadminsecretkey
volumes:
  db_data:

[marionschleifer]

Glad to see that this issue is resolved. I’m closing it 🙂