Add a v4 upgrade guide#277
Conversation
| ## What's in osls v4 | ||
|
|
||
| - **AWS SDK v3**: osls uses the AWS SDK under the hood to interact with AWS. v4 upgrades from the deprecated AWS SDK v2 to v3. | ||
| - **IAM Identity Center (AWS SSO) support**: Thanks to the upgrade to the AWS SDK v3, the `osls` CLI now supports AWS IAM Identity Center (formerly AWS SSO) credentials. |
There was a problem hiding this comment.
@GrahamCampbell have you tested this is working well with the new SDK approach? (before we announce this I just want to make sure)
There was a problem hiding this comment.
I have not tested SSO yet. I was hoping one of the people who opened issues about SSO would test it.
There was a problem hiding this comment.
👍 I need to test it, I haven't even tried v4 yet need to dedicate some time
| | `provider.role` | `provider.iam.role` | | ||
| | `provider.rolePermissionsBoundary` | `provider.iam.role.permissionsBoundary` | | ||
| | `provider.iamRoleStatements` | `provider.iam.role.statements` | | ||
| | `provider.iamManagedPolicies` | `provider.iam.role.managedPolicies` | | ||
| | `provider.cfnRole` | `provider.iam.deploymentRole` | |
There was a problem hiding this comment.
This is something I'd like to revert. It will impact a lot of people for no gain. This was originally deprecated in serverless v2 and for v3 we walked back dropping these because how it was still used a lot. I think it's worth doing the same thing here.
(btw I'm opening this here but not related to this PR directly)
There was a problem hiding this comment.
OK, sure. This will require two PRs. One to adjust v3 to say the removal is in v5 instead. One to re-add it to v4. I can handle that.
2 participants
No description provided.