jkueh / roo Goto Github PK

For my workflow, I need to have a consistent profile name. This aligns with the role I'm trying to assume. Rather than specifying this on the CLI each time, I'd like an option in the configuration file to specify it.

Along with #7, that would allow me to simply type roo delete-prod-role, which would be the ultimate ease-of-use!

Thanks, I hate it.

Output from logs after passing the MFA code input:

2020/12/03 17:49:36 WARNING: Unable to set the file mode on the cache file C:\Users\Jordan Kueh\.roo\cache\[account_number_redacted]-ReadOnly.gob - chmod C:\Users\Jordan Kueh\.roo\cache\[account_number_redacted]-ReadOnly.gob: not supported by windows
2020/12/03 17:49:36 An error occurred while trying to execute command: exec: "/usr/bin/env": file does not exist

Right now everything's command-parameter-y, and while that works, it can be a bit confusing when it comes to behaviour precedence.

It would be good to be able to specify roo write, or roo exec, with each subcommand having their own set of flags.

https://gobyexample.com/command-line-subcommands

This will most likely also resolve #11.

Suggestion came through to allow for a role to be flagged as the 'default' role so that we don't have to provide the -role flag each time, e.g.

roles:
  - name: test
    default: true
    ...

There's only so long I can deal with scrolling through a 300+ line script 😂

To show the configured roles, and their ARNs and aliases.

Need to double check that it works as intended, and document or fix any weird behaviours

I would really like to be prompted for the MFA code, rather than having to specify it on the CLI. Could this please be considered? I think it would make roo easier to use :)

Right now, the version information only appears if you're using a release created via GitHub actions (as it's baked in at build time).

People installing via go get github.com/jkueh/roo will not have a version set, so we'll need to do something about that.

If that's not reasonably possible (e.g. if I don't want to update a package variable every time I'm about to push a tag), then this will be a documentation update for the preferred installation method.

This would be good for a first-run experience, as it'd allow people to immediately start editing a config file.

This is a neat tool! Unfortunately due to $reasons I have some software on my machine that can only authenticate via an AWS profile. It would be awesome if the tool could also write out credentials to a profile, perhaps defined in the config file.

That would allow me to use this with Jetbrains crap the nameless software.

As per guidance here: https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/handling-errors.html

TL;DR: There's a way to handle AWS-specific errors.

To reproduce:

roo -role role_alias_here

Wait for it to prompt for the MFA code, then attempt to hit enter when done - Will keep prompting for MFA code.

e.g. when using roo -role my-alias where a role with the alias my-alias is first in the list of two or more, it will select the second role instead.

Some commands will prompt for user input.

Documentation: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html

This would be useful for those that want to jump into a temporary AWS (web) console session.