Axiom

Hasura presales demo kit

Axiom contains all the resources and tools required to run industry demos of DDN and PromptQL. Within axiom, are a number of different subdirectories with a specific focus, and documentation to support their usage.

Directory	Usage
hasura	Contains all configuration and metadata required to run instances of DDN. hasura includes supergraph, subgraph, and connector metadata for a number of industry demo profiles.
infra	Contains ansible playbooks for the ongoing configuration management of existing demo servers and is used to set up new servers.
scripts	The scripts directory holds useful tools for demoing, managing, and deploying DDN.
.data	Seeds content for local and cloud based demonstrations

Quickstart (Telco)

1. Clone this repo

git clone [email protected]:hasura/axiom.git

2. Install DDN CLI

Follow the DDN CLI installation instructions to download and install DDN CLI

3. Copy .env files

cp hasura/.env.telco.template hasura/.env.telco
cp .data/.env.template .data/telco/.env

4. Run the demo script

cd hasura
ddn run build-telco
ddn run demo-telco

Command Documentation

Each of the ddn run commands in hasura/.hasura/context.yaml corresponds to both a different way to build your supergraph and which source databases to use

Command	Demo Profile	Description
docker-start-telco	Telco	Starts the containers for the telco demo data sources locally
demo-telco	Telco	Starts the containers for the telco demo data sources locally
docker-stop	Any	Stops and removes all Docker containers and volumes related to Axiom

Deployment

Deploying new metadata

Any metadata change that has been tested locally and against CI/CD in a pull request may be rolled out in a couple of seconds with the deploy script.

The deploy script will run a JWT deployment and a No-Auth deployment before applying No-Auth as the project API.

Full documentation may be found in the deploy README

# Run the deploy script
node ./scripts/deploy/deploy.mjs --context axiom-dev --profile telco --no-build-connectors

Deploying new connectors

New connectors should be deployed after connector configuration/schema is updated.

The simplest way to deploy new connectors is to run a new supergraph build in each region. It's important to ensure that the connector regions match the regions you're deploying.

# Deploy new connectors
node ./scripts/deploy/deploy.mjs --context axiom-dev --profile telco --gcp-region gcp-us-west2

Important

Hasura Note: Following a connector update, it's important to update all the .env.cloud.* file details in Confluence. These are not stored in the repo for obvious reasons.

Connectors

Deleting connectors

Sometimes the number of connectors in cloud will surpass the max (100) and it will be required to clear out old connectors.

A handy script has been created to quickly and easily delete older connectors from cloud

Caution

This is a destructive command and will prevent your cloud supergraph from working correctly. Use with caution!

# Delete the 20 oldest connector builds from the default environment in .hasura/context.yaml
./scripts/connector-delete.sh axiom-dev 20