Closed solrevdev closed 4 years ago
given this workflow file for blue-dust-2805
name: Fly Deploy on: push: branches: - master - release/* pull_request: branches: - master - release/* env: FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }} FLY_PROJECT_PATH: backend jobs: deploy: name: Deploy app runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: superfly/flyctl-actions@1.0 with: args: "deploy"
I got this error even though I think the release actually happened on fly.io
##[warning]Unexpected input 'args', valid inputs are [''] Run superfly/flyctl-actions@1.0 with: args: deploy env: FLY_API_TOKEN: *** FLY_PROJECT_PATH: backend /usr/bin/docker run --name be76dbfe59602132f14a0495d77ebdf7dd1963_78b56c --label be76db --workdir /github/workspace --rm -e FLY_API_TOKEN -e FLY_PROJECT_PATH -e INPUT_ARGS -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/blazor-on-vercel/blazor-on-vercel":"/github/workspace" be76db:fe59602132f14a0495d77ebdf7dd1963 deploy ==> Validating app configuration --> done Services TCP 80/443 ⇢ 5000 Deploy source directory '/github/workspace/backend' Docker daemon available, performing local build... Building Dockerfile Using Dockerfile: /github/workspace/backend/Dockerfile deployment-1589890214: digest: sha256:b3bd1bcaaaa0e2b21e2e0a290b7597f51a0566b49dd62a5453881fcd3a12f6b1 size: 1791 --> done ==> Optimizing image --> done ==> Creating Release Release v12 created ==> Monitoring Deployment You can detach the terminal anytime without stopping the deployment Error 1 error occurred: * Cannot return null for non-nullable field Allocation.region
Yesterday it was working and I got this
Run superfly/flyctl-actions@1.0 with: args: deploy env: FLY_API_TOKEN: *** FLY_PROJECT_PATH: backend /usr/bin/docker run --name c27d31516d6e38300242cc92d4ca776ec29818_0b61e3 --label c27d31 --workdir /github/workspace --rm -e FLY_API_TOKEN -e FLY_PROJECT_PATH -e INPUT_ARGS -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_URL -e GITHUB_API_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/blazor-on-vercel/blazor-on-vercel":"/github/workspace" c27d31:516d6e38300242cc92d4ca776ec29818 deploy ==> Validating app configuration --> done Services TCP 80/443 ⇢ 5000 Deploy source directory '/github/workspace/backend' Docker daemon available, performing local build... Building Dockerfile Using Dockerfile: /github/workspace/backend/Dockerfile ==> Creating Release Release v10 created ==> Monitoring Deployment You can detach the terminal anytime without stopping the deployment v10 is being deployed 0b88b98c: ams running unhealthy [canary] [health checks: 1 total] 0b88b98c: ams running healthy [canary] [health checks: 1 total, 1 passing] 0b88b98c: ams running healthy [health checks: 1 total, 1 passing] v10 deployed successfully Creating build context... ⣾
@solrevdev sorry for the trouble! We had in issue with our API that was fixed this morning. Let us know if you have any other issues
@michaeldwan yes all fixed! Re-ran and all good thanks so much
given this workflow file for blue-dust-2805
I got this error even though I think the release actually happened on fly.io
Yesterday it was working and I got this