For users with access to multiple accounts via sts assume-role it takes several steps to get temporary access credentials in order to view flow logs.
This PR automates that process by introducing --role-arn and --external-id command line arguments. These match the AWS CLI arguments.
--external-id doesn't make sense without --role-arn; I check for that and print an error. Using those with --profile may be a little strange, but I didn't forbid it.
Coverage remained the same at 100.0% when pulling c80a19234f6f68b13237621efc036b948979c87b on assume-role into b3e3a1be44952f9b13940e5af575cc7c542ec4a8 on master.
Coverage remained the same at 100.0% when pulling 26dca89304c777f3fde58f4fe1f2a9bd20f811e7 on assume-role into b3e3a1be44952f9b13940e5af575cc7c542ec4a8 on master.
Coverage remained the same at 100.0% when pulling e641366e5b17aa4550bb67706b3a31765dc930d1 on assume-role into b3e3a1be44952f9b13940e5af575cc7c542ec4a8 on master.
Coverage remained the same at 100.0% when pulling eebc6ec2322cb00e7f4592b544e65e2b050ad02a on assume-role into b3e3a1be44952f9b13940e5af575cc7c542ec4a8 on master.
For users with access to multiple accounts via sts assume-role it takes several steps to get temporary access credentials in order to view flow logs.
This PR automates that process by introducing
--role-arn
and--external-id
command line arguments. These match the AWS CLI arguments.--external-id
doesn't make sense without--role-arn
; I check for that and print an error. Using those with--profile
may be a little strange, but I didn't forbid it.