Giters

raisely / deploy

A GitHub action to deploy components and styles to a Raisely campaign

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

CLI/Delpoy works from the terminal, but not from Github action

danalexilewis opened this issue · comments

commented

@tommaitland Hey again, creating the issue on the right repo now.

I haven't had a chance to debug this, and likely will just ignore it as technically its deploying the styles and only failing on the components which is good enough for me for now.

But here you can see the error in the action (also below) and it working in my terminal:

image

******************************
Raisely CLI (1.7.0)
- Uploading styles for ***
******************************
You are about to deploy your local directly to Raisely
    /github/workspace
Using custom API: https://api.raisely.com
You will overwrite the styles and components in your campaign.
✔ Uploading styles for ***
- Uploading component blog-feed
file:///usr/local/lib/node_modules/@raisely/cli/src/actions/api.js:62
		throw new Error(formattedError);
		      ^
Error: https://api.raisely.com/v3/components/2fb72260-06e2-11ed-b[8](https://github.com/bamboocreativenz/livingsober-raisely/runs/7417144838?check_suite_focus=true#step:4:9)5b-[9](https://github.com/bamboocreativenz/livingsober-raisely/runs/7417144838?check_suite_focus=true#step:4:10)f555e27966b (403) failed with message: You are not authorized to do that
    at api (file:///usr/local/lib/node_modules/@raisely/cli/src/actions/api.js:62:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async getComponent (file:///usr/local/lib/node_modules/@raisely/cli/src/actions/components.js:34:9)
    at async updateComponentConfig (file:///usr/local/lib/node_modules/@raisely/cli/src/actions/components.js:63:20)
    at async deploy (file:///usr/local/lib/node_modules/@raisely/cli/src/deploy.js:89:3)
    at async Command.runtime (file:///usr/local/lib/node_modules/@raisely/cli/src/cli.js:[13](https://github.com/bamboocreativenz/livingsober-raisely/runs/7417144838?check_suite_focus=true#step:4:14):3)

lastly here is a link to my Github Action I realised I could dramatically simplify it after our pairing session. Its about as simple as you could get.

commented
commented

@tommaitland blog-feed was a fresh output of ‘raisely create’.

And wouldn’t I I see the syntax error problem when running ‘raisely deploy’ ? Ie the error only happens in the github action.

here’s a link to the components folder

commented

@agentlewis this should be fixed now. We had an error yesterday where about 20% of API requests authenticated with an API key (as the CLI GH action ones are) were failing. That was identified and fixed early yesterday morning, so you shouldn't see this kind of permission error happen again.

Also – can I just ask you to shoot through general troubleshooting things to support@raisely.com? Then we can keep the issues here for CLI improvements and PRs (like some of your other comments).

Reason being is we don't use the Github Issues as a support channel, but we have a whole team on that support@raisely.com email address including technical folk who can help triage and troubleshoot.

commented

@tommaitland thanks for the update.

I suppose from my POV it’s hard to know what’s constitutes general support vs code bug issues.

Also do you have a status page I can look at to see current errors?

mill start with emailing support going forward.

commented

We do! https://status.raisely.com is our general status page, it didn't have the API quirk up there but generally larger incidents are posted to that page pretty quickly such as any kind of service availability issue.