Describe the bug
When running pmapper graph --list, PMapper won't run if the current creds aren't valid. This is due to an optimization where we pull a session from parsed args no matter what we're doing in the graph subcommand.
To Reproduce
Steps to reproduce the behavior, please include information on suspected users/roles that are the source of the issue when possible:
Use PMapper as normal to obtain a graph.
Do something to disable the creds, ensure nothing is available in the default botocore profile, ensure no environment variables with creds are set.
Run pmapper graph --list.
Observe that the command doesn't execute
Expected behavior
A list of available accounts should print no matter what.
We should also throw in the version of PMapper that generated the graph in the list.
Describe the bug When running
pmapper graph --list
, PMapper won't run if the current creds aren't valid. This is due to an optimization where we pull a session from parsed args no matter what we're doing in thegraph
subcommand.To Reproduce Steps to reproduce the behavior, please include information on suspected users/roles that are the source of the issue when possible:
default
botocore profile, ensure no environment variables with creds are set.pmapper graph --list
.Expected behavior A list of available accounts should print no matter what.
We should also throw in the version of PMapper that generated the graph in the list.