vercellone / vsts-f5-tasks Goto Github PK

When running commands from this module, Azure DevOps generates the following warning:

2021-04-12T20:30:54.9082042Z ##[warning]Task 'DisableF5Node' (0.13.0) is using deprecated task execution handler. The task should use the supported task-lib: https://aka.ms/tasklib

We love the module and use it regularly. Can you update it to resolve this?

Computer name resolution and route domain suffix support (i.e. %n) was recently added to the Address parameter in the Posh-LTM-Rest[https://github.com/joel74/POSH-LTM-Rest/] PowerShell Module upon which this extension is based.

Exposing this new functionality is a good first step, but I think some discussion is warranted to get it right.

Blue-Green Deployment - Swap task swaps ALL pending selects within a release, regardless of environment.

It should only swap those selected in the same environment.

Visual Studio marketplace request by Jared Lane.
Verify a target node is healthy before proceeding.

Blue-Green Deployment - Select task writes a CliXml file to the $env:SYSTEM_WORKFOLDER. If Blue-Green Deployment - Swap runs on a different agent with a different $env:SYSTEM_WORKFOLDER, an error will be thrown and the swap will fail.

I currently mitigate this by adding a demand and agent capability which forces both tasks to execute using the same agent.

After upgrading F5 to version 14.1.3.x, from 13.1.3.x this task stopped working.
After some debugging i found that it was during New-F5Session it fails.
The TMError object returned:

System.Management.Automation.CmdletInvocationException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)

By adding this line:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls11
It works again.
Could you update the Task with the TLS 1.1 support?

The Blue-Green Deployment - Swap task is not swapping in all cases. There is no indication when it fails, but the selected pool remains unchanged.