[#651] Allow 'profile ' in ~/.aws/config file sections

[korayal]

closes #651

[endgame]

The code does not compile but the intent seems to be pointing in the right direction. I'll have to read up on the details of the config format AWS uses before coming back to this.

[endgame]

Alternatively, if you can fix the compile errors and then ping me before then, I'll be happy to take another look. Thanks for the PR.

[korayal]

Yeah, sorry about that, I'll fix it in a few hours.

…

On Thu, 30 Sep 2021, 14:01 endgame, ***@***.***> wrote: Alternatively, if you can fix the compile errors and then ping me before then, I'll be happy to take another look. Thanks for the PR. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#654 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACMTSMXCEI53YIN5OGIYCTUEQ7QLANCNFSM5FCAU76A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[korayal]

@endgame I think now this should be good to go, but I have one concern. I can't find the exact documentation on this, but it looks like for named profiles the profile prefix is mandatory, whereas it is not for default.

I wonder if sections like profile default and otherprofile (or even having more than one whitespace between profile and the profile name) are going to be an issue.

I heard from colleagues where stripping profile prefix from sections inside ~/.aws/config does not play well with awscli. So, I've updated the PR to have that prefix for named profiles.

[endgame]

I'll get to it as soon as I can. Meanwhile, can you please rebase against latest develop and add an entry to amazonka/CHANGELOG.md?

[korayal]

done.

[endgame]

@korayal thank you for this.