-
Notifications
You must be signed in to change notification settings - Fork 176
Open
Description
Just started playing around with this. I have a few plugins in the config file, so need to do that.
Config file:
name: Deploy main branch
on:
push:
branches:
- main
jobs:
deploy:
name: deploy
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [18.x]
steps:
- uses: actions/checkout@v3
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v3
with:
node-version: ${{ matrix.node-version }}
- run: npm ci
- name: serverless deploy
uses: serverless/github-action@v3.2
with:
args: -c "cd backend/endpoints && \
serverless plugin install -n serverless-deployment-bucket && \
serverless plugin install -n serverless-python-requirements && \
serverless plugin install -n serverless-iam-roles-per-function && \
serverless plugin install -n serverless-offline && \
serverless deploy"
entrypoint: /bin/sh
env:
SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}
But get the following error:
/bin/sh: 1: serverless: not found
Not sure what exactly needs to be in the package.json
file? I added serverless
as a dep but still the same error.
Metadata
Metadata
Assignees
Labels
No labels
Activity
amirhmk commentedon Jun 28, 2023
Any updates on this? Been stuck with this for a while @dschep?
Tried the appraoch here as well, but still doesn't solve it.
dschep commentedon Jul 6, 2023
I'm not the maintainer, I believe @DavideViolante is currently maintaining this project.
DavideViolante commentedon Jul 6, 2023
I'm also quitting as a maintainer of this project. This repo needs someone from serverless company to maintain it.
dschep commentedon Jul 6, 2023
Agreed. Or just archive it.
levi-20 commentedon Mar 29, 2024
I faced the same issue. I was able to overcome this simply adding a step to install serverless before deployment starts.
dschep commentedon Apr 8, 2024
@ac360, tagging you so someone at serverless is aware this gh action exists without maintainers(afaik)