Open dougmoscrop opened 5 years ago
From your description, I think a --refresh
option on both write
and print
would make sense and be useful. Did I get that right?
Yeah, although I think further to your point, --refresh
should just be the default behaviour!
Or said, "As a developer, I want to type as few things as possible" 😆
bmx [write|print]
should:
default
profile was used, or no pre-existing profile-to-account-and-role mapping exists, or --no-refresh is setIn order to make switching roles possible via interactive prompts, the refresh
flag should default to true, but be able to be disabled bmx print --no-refresh
would stop at 3. and just act like it currently does (selection for account, role, etc.)
bmx renew
did not survive the rewrite from python to golang I think it would be useful to support it.Example:
bmx renew --profile=test-foo
Renew would:
bmx write
--profile would default to
$AWS_PROFILE
if unspecified, allowing users toexport AWS_PROFILE=xyz
and justbmx renew
(all bmx commands should understand and respect AWS_PROFILE in my opinion). I would also argue that renew should be a profile-only command, and I actually completely discourage using default credentials anywhere