-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue in django sls management commands #156
Comments
Indeed, this is the same issue as #132 - serverless started utilizing the I haven't had time to look into it yet, but I think we should consider changing |
I guess if we start brainstorming about it we can end up with some valid candidates for the issue. sls wsgi manage -t "<command_name>"
sls wsgi manage --task "<command_name>" sls wsgi manage -a "<command_name>"
sls wsgi manage --action "<command_name>" sls wsgi manage -x "<command_name>"
sls wsgi manage --execute "<command_name>" And I think that it's better if we just change |
@logandk up |
Sorry, I haven't had any time to spare for this project in a while - I like your first proposal ( |
Awesome! Cheers |
I started to take a look at this, none of the shortcuts were resolving for me until I added
|
Also nothing I tried could get me past the original error I was seeing, maybe the api for invoke has changed?
|
@carlosfunk any ideas on how to solve this? |
You can use
to
same as others command
to:
|
Exacly what we did @himynameisben ! |
Hi People,
I'm using
serverless-wsgi==1.7.6
alongsideserverless==2.2.0
.The problem is when I intend to run a management command as stated in the documents I must be executing this:
But this raises an exception with this error message:
This command is the same as stated in the repo README.md file, but changing
-c
to--command
fixes the problem!So am I missing something here or
-c
is a broken argument?And I would like to contribute to fix the problem, should I be updating the documents or fix handling
-c
arg just like--command
?Any guidance would be appreciated <3
The text was updated successfully, but these errors were encountered: