Closed troyready closed 10 months ago
This improvement has been merged in to master and will be released as part of v2.1.x
@ChrisPates Just was curious when you were planning on releasing v2.1.x? The deprecation date is starting to get closer. Thanks!
I hope to have it released by this time next week. I’m currently updating all the CiCD pipelines to adequately test the new functionality.
Kind regards,
Chris
On 5 Dec 2023, at 18:53, Chris Williams @.***> wrote:
@ChrisPates Just was curious when you were planning on releasing v2.1.x? The deprecation date is starting to get closer. Thanks!
— Reply to this email directly, view it on GitHub https://github.com/awslabs/ssosync/issues/145#issuecomment-1841426824 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVULYIZI7FNYISV7EQAU33YH5URBAVCNFSM6AAAAAA37X5NHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGQZDMOBSGQ . You are receiving this because you were mentioned. https://github.com/notifications/beacon/ABVULYIOJUH3QX7SUY3GWW3YH5URBA5CNFSM6AAAAAA37X5NHWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTNYHYYQ.gif Message ID: @.***>
The ssosync function is deployed using the go1.x runtime, which has been deprecated. In practical terms, this will mean new new deployments will be possible after 2023 and existing deployments will not be able to be updated after 2024-01-31.
Should be simple enough to swap the SAM build fields (unfortunate that there doesn't seem to be a way to pass the
lambda.norpc
golang build tag to slim down the package size but I wouldn't say that's a critical requirement).Also probably worth updating the function architecture to graviton during this update get the price:performance boost.