Hasura setup tasks

[jacqui]

To help keep track of the steps I'm taking... wasn't sure if this warranted a separate repo. I'll update this as I go.

• [x] get to know Hasura CLI
• [x] launch a postgres RDS instance in AWS - hasura-pg-dev, free tier (micro) for now while in development
• [x] create a new project in Hasura
• [x] setup postgres for hasura: https://hasura.io/docs/1.0/graphql/cloud/getting-started/postgres-permissions.html#id1
• [x] NOTE: this was tricky for me to figure out; create the hasura user; grant privileges; create hasura database; connect to hasura db as hasura user; create extension for pgcrypto there; and execute the other required commands; otherwise hasura cannot establish console<->db connection
• [x] create inbound rule on RDS instance allowing traffic to Hasura Cloud IP block
• [x] create a token in Hasura for CLI access: https://accounts.hasura.io/account-settings/access-tokens
• [x] setup organization data model in Hasura (id, name, slug for now)
• [ ] setup content data models - the docs/schema in https://d19u1w7eqbvlum.cloudfront.net/graphql is useful or the source model files
• [ ] all content data models should have an organization_id foreign key
• [ ] initial data for orgs, authors (need more for testing?)
• [ ] start webhook: look up org by slug, return org id header for hasura
• [ ] setup access control in hasura on data
• [ ] author queries and mutations
• [ ] ...

[jacqui]

Database connection: postgres://hasura:ASK ME FOR PASSWORD@hasura-dev.cdrzy2lvikpk.us-east-1.rds.amazonaws.com:5432/hasura_dev

Hasura Project: https://cloud.hasura.io/project/1f4ba420-516e-4b05-8d0e-5b6bcab99c50/details

[jacqui]

I tried to use the hasura cli but I think I must be doing something wrong:

○ → hasura console --endpoint https://tinynews-stack.hasura.app/v1/graphql --log-level DEBUG DEBU global config file exisits, verifying contents DEBU global config is pre-set to &cli.GlobalConfig{UUID:"360ed5cb-b928-4413-a422-d5197a0c3029", EnableTelemetry:true, ShowUpdateNotification:true, CLIEnvironment:"default"} DEBU global config: uuid: 360ed5cb-b928-4413-a422-d5197a0c3029 DEBU global config: enableTelemetry: true
DEBU global config: showUpdateNotification: true
DEBU global config: cliEnvironment: default
DEBU cannot get config information from server, this might be because config API is not enabled: error fetching server config: [not-found] resource does not exist ($) DEBU graphql engine endpoint: https://tinynews-stack.hasura.app/v1/graphql DEBU graphql engine admin_secret:
DEBU versions: cli: [v1.3.3] server: []
DEBU compatibility check: [true] server with no version treated as pre-release build DEBU server state: errors: [json: cannot unmarshal object into Go value of type []util.hdbVersion] DEBU server: uuid: 00000000-0000-0000-0000-000000000000 DEBU response: {"path":"$","error":"resource does not exist","code":"not-found"} DEBU Data Error: {"path":"$","error":"resource does not exist","code":"not-found"} DEBU Data Error: {"path":"$","error":"resource does not exist","code":"not-found"} DEBU telemetry: beamed fields.time=1.384500156s isError=true FATA[0005] error creating migrate instance: cannot create migrate instance: Data Error: {"path":"$","error":"resource does not exist","code":"not-found"}

I'm going to use the web console for now so I'm not stuck.