Skip to content
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

Add option to enable AWS HTTP-level debug logs #877

Closed
EvanBoyle opened this issue Apr 13, 2023 · 1 comment
Closed

Add option to enable AWS HTTP-level debug logs #877

EvanBoyle opened this issue Apr 13, 2023 · 1 comment
Labels
area/providers kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed

Comments

@EvanBoyle
Copy link

The AWS SDK for Go has HTTP-level debug logs that are very helpful in debugging programs that are slow or appear to be stuck. Can we get an env var or config value that turns these logs on within the provider so I can see the output when I run a pulumi program?

c := aws.NewConfig()
c.LogLevel = aws.LogLevel(aws.LogDebugWithHTTPBody)
sess, err := session.NewSession(c)
@EvanBoyle EvanBoyle added the kind/enhancement Improvements or new features label Apr 13, 2023
@kpitzen kpitzen added area/providers resolution/by-design This issue won't be fixed because the functionality is working as designed labels Apr 13, 2023
@kpitzen
Copy link
Contributor

kpitzen commented Apr 13, 2023

We currently implement this within the provider itself by passing -v options to the pulumi cli, along with --logflow, which propagates those options down to plugins. In this case, running: pulumi -v 11 --logflow up will show only the HTTP requests and responses with AWS, and should achieve what's being requested here.

@kpitzen kpitzen closed this as completed Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed
Projects
None yet
Development

No branches or pull requests

2 participants