Node version (10) End of Life

[oguzkilcan]

I have started to receive a warnings on the Node version being end-of-life.

The actual warning message i get is shown below….

[warning]Task 'Terraform Installer' version 1 (TerraformInstaller@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

[warning]Task 'Terraform CLI' version 1 (TerraformCLI@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 believe a small code block inside task.json files is the reason of these warnings: tasks/terraform-installer/task.json tasks/terraform-cli/task.json

"execution": {
        "Node10": {
            "target": ".bin/index.js",
            "argumentFormat": ""
        }
    }```

[JAK1047]

Same here.

[UdayMadamsetty]

Warnings are being reported on Azure DevOps pipeline, even though updated to latest available task version @2. Provided screenshot below for your reference. Could you please help us understand its impact on pipeline runs using these tasks? We are worried on its impact considering deployments to multiple environments through pipelines that are based on these tasks.

[andrei-ivanovici]

Are there any actual hard dependencies on node 10 ? Or is it just a matter of dependencies being out of date ?

[Noel-Jones]

It would appear to be a hard dependency set here https://github.com/jason-johnson/azure-pipelines-tasks-terraform/blob/2d2bf62185e002951bcc370c03efb107fc4c912a/tasks/terraform-installer/task.json#L39 and https://github.com/jason-johnson/azure-pipelines-tasks-terraform/blob/2d2bf62185e002951bcc370c03efb107fc4c912a/tasks/terraform-cli/task.json#L477

[joezuniga19]

Great news this is reported. I initially got this error using the older Charles Zapp version. I reinstalled the new extension from Jason Johnson, and imagine my surprise when the error was still present. I look forward to the progress on this report.

[PratMoha]

Same issue affecting most of our pipelines as well with Node version 10 end of life.

@jason-johnson @charleszipp

[jason-johnson]

For pull request on this issue, it will need to start by checking out the 1. Tag so that the change will back port. 2. Is not considered stable and I think 0. Is actually broken.