Fix assuming a role with an AWS profile

[piohhmy]

What did you implement:

Closes #5673 and #5675

How did you implement it:

Identified that the one line change in #5650 introduced the regression. Changed the clone to be less aggressive to allow tests in #5650 to still pass while fixing the usage of profiles. Honestly, did not look more into exactly why this fixes it, but confirmed it does fix it. I assume it has to do with the deepCopy breaking something once the credentials are passed to sdk in line 269 of lib/plugins/aws/provider/awsProvider.js

How can we verify it:

Try to do any serverless CLI action with an --aws-profile set. Even a simple sls info --aws-profile <profile-name> will hang in versions 1.36+. This PR fixes it.

Todos:

• Write tests
• Write documentation
• Fix linting errors
• Make sure code coverage hasn't dropped
• Provide verification config / commands / resources
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES
Is it a breaking change?: NO

[pmuens]

Nice find. Thanks @piohhmy 👍

[pmuens]

Nice find. Thanks @piohhmy 👍

[pmuens]

Great! Thanks for working on a fix @piohhmy 👍 💯

Can you add a regression test which reproduced the old behavior so that we can be sure that we won't break it again?

I tried to reproduce the issue with my setup, but (un)forunately running (serverless info --aws-profile <my-profile> won't cause the info command to hang. I'm running the latest master 🤔

[pmuens]

Great! Thanks for working on a fix @piohhmy 👍 💯

Can you add a regression test which reproduced the old behavior so that we can be sure that we won't break it again?

I tried to reproduce the issue with my setup, but (un)forunately running (serverless info --aws-profile <my-profile> won't cause the info command to hang. I'm running the latest master 🤔

[pmuens]

D'oh just messed something with the reviews up. Sorry 😬

Pretty sure we're super close to get this in though.

[pmuens]

D'oh just messed something with the reviews up. Sorry 😬

Pretty sure we're super close to get this in though.

[piohhmy]

Ah ok, thanks for taking a look at it @pmuens! I gave it another quick look and you're right, it appears this bug is only when assuming a role via STS. e.g. when you have an aws profile that looks like:

[dummy]
role_arn = arn:aws:iam::111111111111:role/TestRole
source_profile = source

At first glance it may be tricky to write a test case for this as it relies on the AWS SDK behavior of actually getting the async credentials. Perhaps a unit test with some stubbing would be the way to go over an integration test. I can give it a shot in next couple days if this can wait..

[piohhmy]

This also looks like it will fix #5713

[pmuens]

Great! Thanks for taking the time to look into this and explaining the behavior @piohhmy 👍

Perhaps a unit test with some stubbing would be the way to go over an integration test. I can give it a shot in next couple days if this can wait..

Yes that sounds like a good plan. I'd also vote for a simple unit test here. You should find enough examples where we stub the AWS SDK in the test file(s).

Let us know if you need any help 👍

[piohhmy]

@pmuens test added as requested 👍

[pmuens]

Great! Thanks for taking the time to update this @piohhmy 👍

I just pushed merged master into this branch and updated the tests so that it won't error out when one runs it on the local machine with AWS credentials setup.

Tested it and it works on my end.

Will merge once the build is green

[pmuens]

Great! Thanks for taking the time to update this @piohhmy 👍

I just pushed merged master into this branch and updated the tests so that it won't error out when one runs it on the local machine with AWS credentials setup.

Tested it and it works on my end.

Will merge once the build is green