https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
m
Does the logs command even work anymore? It has not worked for me for months 😞
g
@gray-lawyer-89054 This is being tracked at https://github.com/pulumi/pulumi/issues/3448 if you want to upvote that issue.
👍 1
@millions-furniture-75402 I was using it recently. What did you hit? Did you get an error?
m
I don’t receive an error, I just never get logs.
example: if I set up an api gateway to run a lambda, then run 
pulumi logs -f
, and curl the endpoint in another tab, I won’t see anything ever come into the logs. However, if I go to the log group in cloudwatch through the AWS web console, I see logs.
g
If you run with 
pulumi logs -f --logtostderr -v=9
, you might get more information about why.
m
Yes, that’s what I’m running into. Thank you.
The IAM user has AdministratorAccess though.
Okay, that was because I was trying something else with my 
~/.aws/credentials
— The actual error I’m getting is:
Copy code
I0818 10:40:57.261063   60548 operations_aws.go:122] GetLogs[urn:pulumi:develop::adapter-service::aws:apigateway:x:API$aws:apigateway/deployment:Deployment::adapter-service-api] does not produce logs
I0818 10:40:57.409892   60548 operations_aws.go:193] [getLogs] Error getting logs: /aws/lambda/adapter-service-endpoint-137cb12 ResourceNotFoundException: The specified log group does not exist.
I0818 10:40:57.409947   60548 operations_aws.go:107] GetLogs[urn:pulumi:develop::adapter-service::aws:lambda/function:Function::adapter-service-endpoint] return 0 logs
g
Hmm, maybe wrong region being used?
Open in Slack
PreviousNext
Powered by