triggering deploy: unable to create-deployment for app: exit status 1

[z4y4ts]

Hi, for seemingly no reason it started to crash without any help to troubleshoot.

I've tried to re-generate Access token but changed nothing. Although I can see on the DO API Tokens page that the token is actually being used.

My job config is this:

  deploy:
    timeout-minutes: 10
    runs-on: ubuntu-latest
    steps:
    - name: DigitalOcean App Platform deployment
      uses: digitalocean/app_action@v1.1.6
      with:
        app_name: zbx-receivers-app
        token: ${{ secrets.DIGITALOCEAN_ACCESS_TOKEN }}

Here's the GH Action job log: job-logs.txt

[ciderpop]

Same error for me..

Run digitalocean/app_action@v1.1.5
/usr/bin/docker run --name c3483a7367adeddf44713a427329[5](https://github.com/ciderpop/musetheory/actions/runs/8808177659/job/24176745912#step:3:6)18dc497e_819e84 --label 2c3483 --workdir /github/workspace --rm -e "INPUT_APP_NAME" -e "INPUT_TOKEN" -e "INPUT_IMAGES" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_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/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/musetheory/musetheory":"/github/workspace" 2c3483:a7367adeddf44713a427329518dc497e  "" "mt_server" "***"
2024/04/23 22:44:11 triggering deploy: unable to create-deployment for app: exit status 1

[ciderpop]

@z4y4ts was your action working normally before yesterday with that same config?

I just setup actions pipeline for my app platform project yesterday and ran into this on first attempt.

Wasn't sure if it was something on my end or a problem on Digital Ocean's side. Talked to DO support and they had me verify some access token permissions however the issue persists.

[z4y4ts]

As I can see from the workflow logs, the problem appeared 3 days ago - Apr 21st. It worked fine before that.

Can't recall touching the access token anywhere around that time. Also in the job logs, I see GitHub does pass it. Can't check the value though, since it's masked.

[ciderpop]

ah okay I see. yeah my token seems to be setup properly as well and I even tried a full access token instead of custom scopes and same issue, so doesn't seem permissions related.

still waiting to see if their support will advise on this, will report back here if I get any more info from them.

[z4y4ts]

@ciderpop exactly the same thing with the token. Now also waiting for more info from the support.

[educbraga]

Same error here using v1.1.6 :/

[z4y4ts]

yeah, for me v1.1.5 & v1.1.4 are also failing

[arimgibson]

Potentially related issues? #56 #70

I'm just going to double check my app names to make sure because it sounds like that could be related, but glad it's not just me... making me feel like it might be just an outage or something

[arimgibson]

Mine was user error actually... my credentials on DO for pulling my GitHub Container Registry Docker image had expired :sweat_smile: I was able to tell because I couldn't manually deploy from inside DigitalOcean either. Sometimes gotta re-check the basics lol

[ciderpop]

@arimgibson ah yes realized I made a similar mistake! had accidentally had a _ instead of a - for one of the app names so it broke the actions. everything is working properly for me now.

oof very easy rookie mistake I think I need to get my eyes checked now 🤓