Currently the action searches for the Windows executable by looking in three common installation locations and then failing if not found. However, there are other methods available to install it locally (dotnet tools in my case). I propose an additional configuration option to specify the location of sqlpackage.exe or to search for it via the path environment variable. We have self-hosted runners that we try to keep as clean as possible as this reduces the need for software to maintain software on the server.
Currently the action searches for the Windows executable by looking in three common installation locations and then failing if not found. However, there are other methods available to install it locally (dotnet tools in my case). I propose an additional configuration option to specify the location of sqlpackage.exe or to search for it via the path environment variable. We have self-hosted runners that we try to keep as clean as possible as this reduces the need for software to maintain software on the server.