Skip to content
This repository has been archived by the owner on Dec 19, 2022. It is now read-only.

rdslogs doesn't respect AWS_DEFAULT_PROFILE environment variable #9

Closed
gchpaco opened this issue Sep 22, 2017 · 3 comments
Closed

rdslogs doesn't respect AWS_DEFAULT_PROFILE environment variable #9

gchpaco opened this issue Sep 22, 2017 · 3 comments

Comments

@gchpaco
Copy link

gchpaco commented Sep 22, 2017

I have separate profiles, and as it happens for my configuration the default profile didn't have useful credentials. I have the AWS_DEFAULT_PROFILE environment variable set normally, but that wasn't getting passed along when I ran rdslogs.
@garthk
Copy link

garthk commented May 10, 2018 •
edited
Loading

Nor, AWS_PROFILE. The strikeouts in the README tell me it's a known problem, but this is the only issue I can find for it someone forgot some back-ticks.

garthk pushed a commit to garthk/rdslogs that referenced this issue May 11, 2018
Escape more CLI detail for greater clarity
25916e6 
Having mis-read some accidental strikethrough in the README as deliberate
(honeycombio#9), I now feel compelled to ESCAPE ALL THE THINGS. Also:

* Linked to the documentation on where to find the binary packages, as
  I initially couldn't find them

* Tweaked a few links to Honeycomb based on whether they seemed to be
  referring to the service or to the web site

* Verified the last block of `--help` output is still correct (yep!)

* Added language identifiers to the GFM fenced code blocks that didn't
  have them, as some renderers were guessing differently between the
  first two examples

I couldn't figure out whether Ben intended to keep the command line session
extract below the Usage heading or make it more texty, and chose to double
down on the former.
@garthk garthk mentioned this issue May 11, 2018
Merged
@garthk
Copy link

garthk commented May 11, 2018

6a878be on macOS 10.13.4:

$ export AWS_PROFILE=xxx
$ rdslogs --region ap-southeast-2 --dbtype=postgresql
Sending output to STDOUT
2018/05/11 11:00:57 Unable to locate credentials. You can configure credentials by running "aws configure".

dtruss shows opening ~/.aws/credentials. I can't find a read, but it might be a red herring.

89391/0x1a7a351:  open("/Users/self/.aws/credentials\0", 0x1000000, 0x0)		 = 3 0
…
89391/0x1a7a351:  fcntl(0x3, 0x3, 0x0)		 = 0 0
89391/0x1a7a351:  fcntl(0x3, 0x4, 0x4)		 = 0 0
89391/0x1a7a351:  close(0x3)		 = 0 0

Perhaps I'm running into aws/aws-sdk-go#1019, which is a pity because its maintainers seem to have decided the mismatch between the Go SDK and other language SDKs is not a bug and, given the age, not urgent. Perhaps it's back-pressure from the combination of Go's dependency management challenges and the idea that matching the other SDKs would be a breaking change, in particular for AWS_DEFAULT_PROFILE, which is tough luck for @gchpaco (see aws/aws-sdk-go#554).

@MikeGoldsmith
Copy link
Contributor

We’re going to close this for now. Feel free to re-open if it’s still relevant.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@garthk @gchpaco @MikeGoldsmith