SQL Aliases are not used

[droyad]

Team

• I've assigned a team label to this issue

Severity

Blocking some customers, but workaround is available

Version

2021.2 and 2021.3

Latest Version

I could reproduce the problem in the latest build

What happened?

When we upgraded Octopus Server to .NET 5.0, the SQL Alias mapping stopped working due to droyad/SqlAlias#7 which detected whether it was .NET Core and the aliasing needed to be applied. .NET 5 no longer identifies itself as ".NET Core".

Reproduction

Add an alias
Configure octopus to use that sql alias
Server won't start

Error and Stacktrace

No response

More Information

No response

Workaround

Use the unaliased name of the server

[octoreleasebot]

Release Note: SQL Aliases can be used again for server connection strings

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2021.2	2021.2.8001
2021.3	2021.3.10803
2022.1+	all releases