Revert "Merge release/trigger to main (#913)"

This reverts commit a4f3a30.

Author: MaddyDev

.vscode/settings.json

@@ -8,6 +8,6 @@
     "omnisharp.enableEditorConfigSupport": true,
     "omnisharp.enableRoslynAnalyzers": true,
     "yaml.schemas": {
-         "https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json": "builds/azure-pipelines/**/*.yml"
-     },
+        "https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json": "builds/azure-pipelines/**/*.yml"
+    },
 }

Directory.Packages.props

@@ -15,7 +15,6 @@
     <PackageVersion Include="Moq" Version="4.18.4" />
     <PackageVersion Include="xunit" Version="2.5.0" />
     <PackageVersion Include="xunit.runner.visualstudio" Version="2.5.0" />
-    <PackageVersion Include="xRetry" Version="1.9.0" />
     <PackageVersion Include="Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator" Version="4.0.1" />
     <PackageVersion Include="Newtonsoft.Json" Version="13.0.3" />
     <PackageVersion Include="Microsoft.AspNetCore.Http" Version="2.2.2" />

README.md

@@ -1,14 +1,13 @@
-# Azure SQL bindings for Azure Functions - Preview
+# Azure SQL bindings for Azure Functions
 
 ## Table of Contents
 
-- [Azure SQL bindings for Azure Functions - Preview](#azure-sql-bindings-for-azure-functions---preview)
+- [Azure SQL bindings for Azure Functions](#azure-sql-bindings-for-azure-functions)
   - [Table of Contents](#table-of-contents)
   - [Introduction](#introduction)
   - [Supported SQL Server Versions](#supported-sql-server-versions)
   - [Known/By Design Issues](#knownby-design-issues)
     - [Output Bindings](#output-bindings)
-    - [Trigger Bindings](#trigger-bindings)
   - [Telemetry](#telemetry)
   - [Privacy Statement](#privacy-statement)
   - [Trademarks](#trademarks)
@@ -19,7 +18,7 @@ This repository contains the Azure SQL bindings for Azure Functions extension co
 
 - **Input Binding**: takes a SQL query or stored procedure to run and returns the output to the function.
 - **Output Binding**: takes a list of rows and upserts them into the user table (i.e. If a row doesn't already exist, it is added. If it does, it is updated).
-- **Trigger Binding**: monitors the user table for changes (i.e., row inserts, updates, and deletes) and invokes the function with updated rows.
+- **Trigger (preview)**: monitors the user table for changes (i.e., row inserts, updates, and deletes) and invokes the function with updated rows. Note: This is a preview feature and is available only in preview packages. More information is available on the [trigger branch](https://github.com/Azure/azure-functions-sql-extension/tree/release/trigger) and on the [documentation](https://aka.ms/sqltrigger).
 
 For a more detailed overview of the different types of bindings see the [Bindings Overview](https://github.com/Azure/azure-functions-sql-extension/blob/main/docs/BindingsOverview.md).
 
@@ -46,7 +45,7 @@ Below is a list of common issues that users may run into when using the SQL Bind
 
 > **Note:** While we are actively working on resolving the known issues, some may not be supported at this time. We appreciate your patience as we work to improve the Azure Functions SQL Extension.
 
-- **By Design:** The table used by a SQL binding or SQL trigger cannot contain two columns that only differ by casing (Ex. 'Name' and 'name').
+- **By Design:** The table used by a SQL binding cannot contain two columns that only differ by casing (Ex. 'Name' and 'name').
 - **By Design:** Non-CSharp functions using SQL bindings against tables with columns of data types `BINARY` or `VARBINARY` need to map those columns to a string type. Input bindings will return the binary value as a base64 encoded string. Output bindings require the value upserted to binary columns to be a base64 encoded string.
 - **Planned for Future Support:** SQL bindings against tables with columns of data types `GEOMETRY` and `GEOGRAPHY` are not supported. Issue is tracked [here](https://github.com/Azure/azure-functions-sql-extension/issues/654).
 - Issues resulting from upstream dependencies can be found [here](https://github.com/Azure/azure-functions-sql-extension/issues?q=is%3Aopen+is%3Aissue+label%3Aupstream).
@@ -68,10 +67,6 @@ Below is a list of common issues that users may run into when using the SQL Bind
   - PowerShell: The workaround is to use the `$TriggerMetadata[$keyName]` to retrieve the query property - an example can be found [here](https://github.com/Azure/azure-functions-sql-extension/blob/main/samples/samples-powershell/AddProductParams/run.ps1). Issue is tracked [here](https://github.com/Azure/azure-functions-powershell-worker/issues/895).
   - Python: The workaround is to use `parse_qs` - an example can be found [here](https://github.com/Azure/azure-functions-sql-extension/blob/main/samples/samples-python/AddProductParams/__init__.py). Issue is tracked [here](https://github.com/Azure/azure-functions-python-worker/issues/894).
 
-### Trigger Bindings
-
-- **By Design:** Trigger bindings will exhibit undefined behavior if the SQL table schema gets modified while the user application is running, for example, if a column is added, renamed or deleted or if the primary key is modified or deleted. In such cases, restarting the application should help resolve any errors.
-
 ## Telemetry
 
 This extension collects usage data in order to help us improve your experience. The data is anonymous and doesn't include any personal information. You can opt-out of telemetry by setting the `AZUREFUNCTIONS_SQLBINDINGS_TELEMETRY_OPTOUT` environment variable or the `AzureFunctionsSqlBindingsTelemetryOptOut` app setting (in your `*.settings.json` file) to '1', 'true' or 'yes';

Worker.Extensions.Sql/src/SqlChange.cs

@@ -25,7 +25,7 @@ steps:
       $source = 'java-library'
       $destination = '$(Build.ArtifactStagingDirectory)/java-library'
       $jar = Get-ChildItem $source/target/*.jar | Select-Object -First 1 | Select Name
-      $jar -match '\d+\.\d+\.\d+(-preview)?'
+      $jar -match '\d+\.\d+\.\d+'
       $version = $matches[0]
       $prefix = 'azure-functions-java-library-sql-'+$version
       New-Item $destination -ItemType Directory

Worker.Extensions.Sql/src/SqlTriggerAttribute.cs

@@ -4,7 +4,7 @@ parameters: # parameters are shown up in ADO UI in a build queue time
 - name: 'ReleaseType'
   displayName: 'Type of release'
   type: string
-  default: preview
+  default: full
   values:
     - full
     - preview
@@ -22,7 +22,7 @@ schedules:
 variables:
   solution: '**/*.sln'
   configuration: 'Release'
-  versionMajor: 3
+  versionMajor: 2
   versionMinor: 0
   versionMajorMinor: '$(versionMajor).$(versionMinor)'  # This variable is only used for the counter so we reset properly when either major or minor is bumped
   versionPatch: $[counter(variables['versionMajorMinor'], 0)] # This will reset when we bump minor version

builds/azure-pipelines/build-release-java.yml

@@ -2,13 +2,7 @@ trigger: none
 
 pr: none
 
-schedules:
-  - cron: "0 0 * * *"
-    displayName: Mon-Fri at Midnight
-    branches:
-      include:
-        - main
-    always: true
+schedules: [ ]
 
 variables:
   configuration: 'Release'

builds/azure-pipelines/build-release.yml

@@ -9,11 +9,6 @@ parameters:
     default:
       - input
       - output
-      - trigger
-      - trigger_batch
-      - trigger_poll
-      - trigger_overrides
-      - trigger_parallel
 
 steps:
 - task: UseDotNet@2