serverless / serverless/serverless
Serverless command "deploy" not found
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Are you certain it's a bug?
- Yes, it looks like a bug
Is the issue caused by a plugin?
- It is not a plugin issue
Are you using the latest v3 release?
- Yes, I'm using the latest v3 release
Is there an existing issue for this?
- I have searched existing issues, it hasn't been reported yet
Issue description
Hello, i am trying to deploy to azure but deploy is not recognized, i have used serverless to deploy to AWS before.
I also ran the command npm install --save serverless-azure-functions and serverless is installed.
Service configuration (serverless.yml) content
`service: azure-python-service
provider:
name: azure
location: eastus
runtime: python3.8
functions:
pythonSAP:
handler: handler.main
events:
- http: true
x-azure-settings:
authLevel: anonymous
methods:
- get
`
Command name and used flags
serverless deploy
Command output
Environment: linux, node 18.16.0, framework 3.33.0, plugin 6.2.3, SDK 4.3.2
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
Serverless command "deploy" not found. Run "serverless help" for a list of all available commands.
Environment information
Environment: linux, node 18.16.0, framework 3.33.0, plugin 6.2.3, SDK 4.3.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing serverless deploy with the provided serverless.yml, then compare its output with serverless help in the stated Linux, Node 18.16.0, and Framework 3.33.0 environment. Done means the Azure service configuration exposes the expected deploy command and the command no longer reports deploy as missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100