aws-toolkit-azure-devops
aws-toolkit-azure-devops copied to clipboard
aws
ECRPushImage warning in Azure Devops due to Node10 dependency
The ECRPushImage Task uses Node10 which is no longer supported . This causes a warning to be displayed on our build process in Azure Devops
##[warning]Task 'Amazon ECR Push' version 1 (ECRPushImage@1) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance
This isn't just limited to ECR - we're getting the same on AWSShellScript:
##[warning]Task 'AWS Shell Script' version 1 (AWSShellScript@1) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance
I suspect the whole toolkit needs a v2 with a node update.
AWS support ADO seems pretty dead. I wish I was stuck with ADO either :/
I found out why they don't just bump the Node version. From PR #560:
Supporting node 16 requires bumping azure-pipelines-task-lib. We are currently blocked from doing this because this version bump uses a newer version of shelljs as a dependency, which produces runtime errors for our task. (see PR description in https://github.com/aws/aws-toolkit-azure-devops/pull/539 for more details).
Just to add, also seeing this on SystemsManagerGetParameter@1 task too:
##[warning]Task 'AWS SSM Get Parameter' version 1 (SystemsManagerGetParameter@1) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance
Just to add to the pile, we are seeing this on S3Upload, AWSShellScript.
We are also seeing the same on Terraform and Terraform-outputs. Different extensions, but the same issue.
Same issue here for the AWSCLI, AWSShellScript, LambdaDeployFunction and ECRPushImage on our end. My guess is all the tasks for the aws-toolkit-azure-devops are affected by this.
Seeing the same over in our org. No new information, just leaving this comment to help express the potential impact of this deprecation.
Its a on going issue with AWS and Terraform , fixed terraform issue by upgrading its version But AWSShellScript , AWSCLI issue is consistent even after version upgrade
+1. Getting the same error for all tasks used from aws-toolkit-azure-devops. Would be good to know the timeline when it is expected to be upgraded.
See https://github.com/jfrog/jfrog-azure-devops-extension/pull/518 for inspiration on addressing the issue. This seems to have worked for the JFrog marketplace extension, and the warning is no longer appearing.
Anyone have an official Microsoft doc that states when they are pulling the plug on node v10?
I opened an AWS support ticket and I can tell you AWS is aware of this.
I like to acknowledge that we are aware of this problem. In our past attempts to address this, we got blocked by a shelljs related JS bundler issue which prevented us from updating azure-pipelines-task-lib. We are looking into this again and will post an update once we have more information.
I like to acknowledge that we are aware of this problem. In our past attempts to address this, we got blocked by a shelljs related JS bundler issue which prevented us from updating
azure-pipelines-task-lib. We are looking into this again and will post an update once we have more information.
Is there a timeline when this is planned to be resolved?
Is there a timeline when this is planned to be resolved?
Not yet, but we will share more information once we have an update. Thank you for your patience.
Hey @saurabhajmera
Is there any updates regarding this ongoing issue ?
@ajith-shan-m, We are actively working on a short-term solution, which we plan to release in the coming weeks. Addressing the shelljs issue in the long term, however, will require changes to the azure-pipelines-task-lib library, which is maintained by Microsoft. While we are in ongoing communication with Microsoft about this, we currently do not have a timeline for when the long-term fix will be available.
We have updated the tasks to support Node 20 as per microsoft guidance. It is now released under version 1.18.0
Same here! Thanks!
On 10 Dec 2024, at 7:05 PM, Ryan Pendergast @.***> wrote:
I have confirmed the warning has gone away. Thanks!
— Reply to this email directly, view it on GitHub https://github.com/aws/aws-toolkit-azure-devops/issues/566#issuecomment-2533019467, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJXS3GS2BNVT5WFAB6656T2E5QQ5AVCNFSM6AAAAABO2OVB4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGAYTSNBWG4. You are receiving this because you are subscribed to this thread.
I can see in my pipeline that it lists 1.18
Task : Amazon S3 Upload
Description : Upload file and folder content to an Amazon Simple Storage Service (S3) Bucket on AWS
Version : 1.18.0
But I still seeing it using node10\bin\node.exe in an error we are facing. Is this change dependent on anything other than just having the newest version of the task?
I can see in my pipeline that it lists 1.18
Task : Amazon S3 Upload Description : Upload file and folder content to an Amazon Simple Storage Service (S3) Bucket on AWS Version : 1.18.0But I still seeing it using
node10\bin\node.exein an error we are facing. Is this change dependent on anything other than just having the newest version of the task?
The change allows agents to use node 20 to run the tasks, so it seems likely that your agent either does not have node 20 installed or it is not the default. AFAIK, in most cases microsoft-hosted agents should already have node20 installed and used by default, while on-prem agents will need to be manually updated (if not already done so by now).
Can you verify the agent it is running on has node 20 and it's the default? Try using the Node JS installer task in your pipeline before running the AWS tasks. If you still see this, please open a new issue.