Skip to content
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.

Does this still work? Getting a 403 #4

Open
kchro3 opened this issue Jul 2, 2024 · 0 comments
Open

Does this still work? Getting a 403 #4

kchro3 opened this issue Jul 2, 2024 · 0 comments

Comments

@kchro3
Copy link

kchro3 commented Jul 2, 2024

My github action is set up as:

  deploy:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    steps:
      - uses: actions/checkout@v4

      - name: Build & Deploy Worker
        uses: cloudflare/wrangler-action@v3.5.0
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}

      - uses: baselime/action-setup-baselime@v0.0.1
        with:
          baselime-api-key: ${{ secrets.BASELIME_API_KEY }}
          
      - name: 📍Create marker
        run: |
          baselime mark \
          --name Deployment \
          --url "${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}" \
          --metadata '${{ toJson(github) }}' \
          --service ${{ github.repository }}

I'm getting this:

baselime mark \
  --name Deployment \
  ... redacted
  shell: /usr/bin/bash -e {0}
Attention: Baselime now collects completely anonymous telemetry regarding usage. This is used to guide our roadmap.
You can learn more, including how to opt-out of this anonymous program, by heading over to:
https://baselime.io/docs/cli/anonymous-telemetry

- Creating marker
✖ Creating marker
Error - Forbidden
✖ Error - Request failed with status code 403
Use the --debug flag to view the complete stack trace.
Error: Process completed with exit code 1.

And i do have the secret set up
Screenshot 2024-07-02 at 12 08 58 PM

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant