I cannot seem to figure out how to allow a
service to ping any http server that was spun up during each step.
Rough concept of action below.
- Postgres/Hasura spin up.
- Steps run and executes a node server
- Hasura needs to be able to communicate to the node server that was created
name: Test on: push: branches: test/** paths: - "test/**" jobs: build: runs-on: ubuntu-latest services: postgres: image: postgres:12.1 env: POSTGRES_USER: postgres POSTGRES_DB: postgres ports: - 5432:5432 options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 hasura: image: hasura/graphql-engine:v1.3.2 env: HASURA_GRAPHQL_DATABASE_URL: postgres://postgres:@postgres:5432/postgres HASURA_GRAPHQL_ENABLE_CONSOLE: "true" HASURA_GRAPHQL_DEV_MODE: "true" HASURA_GRAPHQL_LOG_LEVEL: debug HASURA_GRAPHQL_ENABLED_APIS: metadata,graphql HASURA_GRAPHQL_ADMIN_SECRET: admin_secret ACTION_SCHEMA_BASE_URL: http://localhost:9999/api/graphql options: >- --health-cmd "wget --quiet --spider http://localhost:8080/healthz" --health-interval 30s --health-timeout 3s ports: - 8080:8080 steps: - uses: actions/checkout@v2 - uses: bahmutov/npm-install@v1 with: working-directory: test - name: Run test # Hasura service needs to access this working-directory: test run: | yarn dev & yarn wait - name: Hasura CI/CD uses: GavinRay97email@example.com with: PATH_TO_HASURA_PROJECT_ROOT: hasura HASURA_CLI_VERSION: v1.3.2 HASURA_ENDPOINT: http://hasura:8080 HASURA_ADMIN_SECRET: admin_secret HASURA_MIGRATIONS_ENABLED: true