🐛 fix for a non-standard port not being properly parsed, surfaced in #161 where connectivity to Azure SQL Managed Instance public endpoint would fail

thanks to @miljann995 for the collaboration!

🎉 This release moves to go-sqlcmd v1

go-sqlcmd powers parts of sql-action and has recently moved to their v1 release, announcement here completed in #176

🤖 Improvements by dependabot

• #175 Removes xml2js
• #175 Updates @azure/keyvault-keys from 4.4.0 to 4.7.0

🐛 fix for Expand-Archive : is not a supported... #149, where some Windows environments may have a version of PowerShell not compatible with unzipping files without a file extension

The v2.1 release introduces a few improvements:

• Support for Node16 #150
• Support for go-sqlcmd v0.12.0 #163
• 🐛 fix for DriftReport #167
• 🐛 fix for arguments not being passed to sqlcmd #145

❤️ thanks to @emil-eklund and @JoshFieldstad for contributions to this release!

🎉 The v2 release introduces a few improvements:

1. AAD authentication with username/password, service principal, and managed identity (#60, #78, #93)
2. Support for access with login credentials that do not have access to master

🛠️ Breaking changes

1. The action switched from sqlcmd to go-sqlcmd for script execution. It will automatically install the latest go-sqlcmd if it is not found.
2. The action's yaml input format has been changed. This includes removal of server-name.

- uses: azure/sql-action@v2
  with:
    # required, connection string incl the database and user authentication information
    connection-string:

    # required, path to either a .sql, .dacpac, or .sqlproj file
    path:

    # optional when using a .sql script, required otherwise
    # sqlpackage action on the .dacpac or .sqlproj file, supported options are: Publish, Script, DeployReport, DriftReport
    action:

    # optional additional sqlpackage or go-sqlcmd arguments
    arguments:

    # optional additional dotnet build options when building a database project file
    build-arguments:

The v1.3 release introduces 1 improvement:

1. 🛠 Option to start from project-file to build and publish, #65

We're beginning to plan and work on a v2 of sql-action, check out more details in #98!

The v1.2 release introduces 1 improvement, related to 1 fix:

1. 🏎 The action is packaged with webpack, reducing the download size to improve the performance of your pipelines. #69
2. 🐛 The use of webpack fixes the accidental removal of node_modules from release v1.1. #70

❤️ Thank you @mayong43111 for the contributions to the webpack improvements!

🎉 The v1.1 release introduces 2 improvements:

1. The action is supported in Linux environments (for example: runs-on:ubuntu-latest) for both dacpac deployment and SQL script execution.
2. The server-name input parameter is now optional. This change is non-breaking - if server-name is present, that value will be used instead of the server name specified in the connection string.

❤️ Thank you @zijchen, @caohai, @yorek, and @llali for contributions to these changes and code health!

Automate your Action workflows to deploy to an Azure SQL database using this option

Sample workflow to deploy to an Azure SQL database

# .github/workflows/sql-deploy.yml
on: [push]

jobs:
  build:
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@v1
    - uses: azure/actions/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}
    - uses: Azure/sql-action@v1
      with:
        server-name: REPLACE_THIS_WITH_YOUR_SQL_SERVER_NAME
        connection-string: ${{ secrets.AZURE_SQL_CONNECTION_STRING }}
        dacpac-package: './Database.dacpac'

Released under MIT License