We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I just spent a few minutes wondering why I wasn't seeing any log output. 😂
I was using saw get /aws/lambda/<group_name> but forgot to add --start -10m to the end of the command.
saw get /aws/lambda/<group_name>
--start -10m
The default is time.Now() so I wasn't seeing any logs.
time.Now()
saw/config/configuration.go
Lines 84 to 92 in 77bbab2
AWS SAM [1] and Serverless Framework [2] both use -10m as their default for log retrieval, whereas saw uses the current time.
-10m
saw
Seems like a straightforward change to set the empty string "" to -10m to match.
""
saw/cmd/get.go
Lines 42 to 51 in 77bbab2
What do you think? I've applied it in my fork, and am using it. Happy to PR.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I just spent a few minutes wondering why I wasn't seeing any log output. 😂
I was using
saw get /aws/lambda/<group_name>
but forgot to add--start -10m
to the end of the command.The default is
time.Now()
so I wasn't seeing any logs.saw/config/configuration.go
Lines 84 to 92 in 77bbab2
AWS SAM [1] and Serverless Framework [2] both use
-10m
as their default for log retrieval, whereassaw
uses the current time.Seems like a straightforward change to set the empty string
""
to-10m
to match.saw/cmd/get.go
Lines 42 to 51 in 77bbab2
What do you think? I've applied it in my fork, and am using it. Happy to PR.
The text was updated successfully, but these errors were encountered: