Deploy not configured error in github action

[WillHWThompson]

I am trying to deploy my dashboard via a github action following the documentation here.

Here is the

name: Deploy

on:
  push:
    branches: [main]
  schedule: 
    - cron: "15 10 * * *"
  workflow_dispatch: {}

jobs:
  build_and_deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm

      - name: Set up Python
        uses: actions/setup-python@v4
        with:
          python-version: '3.9.16'

      - name: Cache Python packages
        id: cache-python-packages
        uses: actions/cache@v3
        with:
          path: ~/.cache/pip
          key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
          restore-keys: |
            ${{ runner.os }}-pip-

      - name: Install dependencies
        run: |
          pip install -e .

      - name: Cache databases directory
        id: cache-databases
        uses: actions/cache@v3
        with:
          path: databases
          key: ${{ runner.os }}-databases-${{ hashFiles('dashboard_src/create_database.py') }}
          restore-keys: |
            ${{ runner.os }}-databases-

      - name: Check Cache Hit Status
        run: |
          echo "Cache hit: ${{ steps.cache-databases.outputs.cache-hit }}"

      - name: Pull newest data from Airtable
        if: steps.cache-databases.outputs.cache-hit != 'true'
        run: |
          mkdir -p databases
          python dashboard_src/create_database.py
          
      - run: npm ci
      - run: npm run build 

      - name: Deploy to Observable Cloud
        run: |
          npm run deploy --deploy-config=docs/.observablehq/deploy.json --debug --message "$(git log -1 --pretty=%s)"
        env:
          OBSERVABLE_TOKEN: ${{ secrets.OBSERVABLE_TOKEN }}

And my deploy.json looks like this:

{
  "projected": "<project_id>",
   "projectSlug": "<project slug>",
    "workspaceLogin": "<login>"
  }

I have verified that the OBSERVABLE_TOKEN is indeed configured in the repo.

I can deploy locally perfectly fine, but when I run the GitHub action I get the following error:

Run npm run deploy --deploy-config=docs/.observablehq/deploy.json --debug --message "$(git log -1 --pretty=%s)"

> deploy
> observable deploy

┌   observable deploy 
│
└  Error: Deploy not configured.

Error: Process completed with exit code 1.

Where else can I look for a problem? I've verified the Observable token and explicitly set the path to the deploy.json file. What else could be causing the error?

[Fil]

I think you need to add -- after npm run deploy to separate the options, like so:

npm run deploy -- --deploy-config=docs/.observablehq/deploy.json --debug --message "$(git log -1 --pretty=%s)"

[mythmon]

As well as Fil's note about --, the option you are passing for --deploy-config seems to be the default value. You could leave it off.

I notice that there is a problem in your deploy.json. You have "projected": "<project_id>" when the key should be "projectId".

[WillHWThompson]

Hmm, the "projected" was a typo copying the file text into the discussion thread. The file itself says "projected".

I amended the -- and I still get the same Error: Deploy not configured.

What else besides the deploy.json files needs to be configured for the deploy to work properly? Again the deploy works locally so it has to be some difference between the state of my local repo and the remote machine configured by GitHub action. I'm really at a loss. Any help on de-bugging directions would be much appreciated.

[mythmon]

The file itself says "projected".

Did you typo "projectId" again there?

Maybe a dumb question, but have you committed the deploy.json file to git on the branch that GitHub is building? That file should be the only thing that is needed.

Specifically what is happening is that when Framework doesn't find the file or finds that it is not the right format, it tries to prompt the user to deploy. In GitHub actions it can't prompt (since it is a non-interactive terminal), and so it fails with that error.

If that file is definitely committed, I'd recommend deleting it, deploying by hand without a --deploy-config parameter to regenerate the file, and then committing and pushing the new file without editing it. That can help eliminate any other syntax problems with the file.