search

awslabs / aws-greengrass-group-setup

File-driven creation of an entire AWS Greengrass group
Apache License 2.0
53 stars 23 forks source link

Profile name not actually being used #10

Closed elison-chen closed 6 years ago

elison-chen commented 6 years ago

Looks like GroupCommands accepts a profile_name parameter, but afterwards it never uses it.

_get_iot_session function also takes in a profile_name as a parameter, but no usages of this function actually pass in the profile_name.

This should be remedied so that people can pass in different profiles to edit/create Greengrass groups in different accounts.

The current work around is to change the default in ~/.aws/credentials depending on which account you want to modify.

brettf commented 6 years ago

@elison-chen Although I know it has been some time, I wanted you to know this has been resolved. Please validate that your needs around using AWS CLI profile values work.

Sandmania commented 5 years ago

Hmm, this doesn't seem to work. Things get created to the default profile even though --profile-name is provided with gg_group_setup create-core