Support for --duration-seconds about assume-role

[ejholmes]

@mthenw that'd be great!

[mthenw]

Any idea how this could look like as assume-role doesn't support named parameters? It's tricky because everything after role is treated as a command to exec.

[ejholmes]

Right now, it uses os.Args to grab the command and arguments to pass, but if you use the standard flag package, then flag.Args() returns all of the positional arguments after the flags, so we can do:

$ assume-role --duration-seconds 60 <role>

[dlovitch]

Because of the new blog post announcing limits up to 12 hours, I get the sense that this feature could be even more useful: https://aws.amazon.com/blogs/security/enable-federated-api-access-to-your-aws-resources-for-up-to-12-hours-using-iam-roles/

[RichardBronosky]

Was this created before there was a --duration arg that accepts 12h? If so, can this be closed?

[dlovitch]

I haven't used assume-role in a long while now, but it does seem like it based on 7d9496a which happened a couple of months after this issue was opened.

[russellballestrini]

Yeah, I'm going to close this as fixed. At somepoint the --duration flag was introduced so this feature request is solved.

@mthenw I'm assuming --duration in hours is a suitable solution to what you had in mind regarding --duration-seconds?