Adding errorOnInvalidSubstitution checkbox (#20858)

Author: EshitaD

Tasks/FileTransformV2/Strings/resources.resjson/en-US/resources.resjson

@@ -15,6 +15,8 @@
   "loc.input.help.jsonTargetFiles": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;\"Data\": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;\"DefaultConnection\": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> } <br/> Variable Substitution is run after configuration transforms. </br> </br> Note: Only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables. ",
   "loc.input.label.xmlTargetFiles": "XML target files",
   "loc.input.help.xmlTargetFiles": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder. <br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. <br/> Variable Substitution is run after configuration transforms. </br> Note: Only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.",
+  "loc.input.label.errorOnInvalidSubstitution": "Error on empty files and invalid substitution.",
+  "loc.input.help.errorOnInvalidSubstitution": "If selected, the pipeline fails if the target files are empty or if the substitution fails.",
   "loc.messages.JSONvariablesubstitutionappliedsuccessfully": "JSON variable substitution applied successfully.",
   "loc.messages.FailedToApplyJSONvariablesubstitution": "Failed to apply JSON variable substitution.",
   "loc.messages.FailedToApplyJSONvariablesubstitutionReason1": "Failed to apply JSON variable substitution. Changes are already present in the package.",

Tasks/FileTransformV2/_buildConfigs/Node20/package-lock.json

@@ -20,7 +20,7 @@
     "@types/mocha": "^5.2.7",
     "@types/node": "^20.3.1",
     "@types/q": "1.0.7",
-    "azure-pipelines-tasks-webdeployment-common": "4.252.0",
+    "azure-pipelines-tasks-webdeployment-common": "4.253.0",
     "q": "1.4.1"
   },
   "devDependencies": {

Tasks/FileTransformV2/_buildConfigs/Node20/package.json

@@ -20,7 +20,7 @@
     "@types/mocha": "^5.2.7",
     "@types/node": "^20.3.1",
     "@types/q": "1.0.7",
-    "azure-pipelines-tasks-webdeployment-common": "4.252.0",
+    "azure-pipelines-tasks-webdeployment-common": "4.253.0",
     "q": "1.4.1"
   },
   "devDependencies": {

Tasks/FileTransformV2/package-lock.json

@@ -17,7 +17,7 @@
   ],
   "version": {
     "Major": 2,
-    "Minor": 252,
+    "Minor": 253,
     "Patch": 0
   },
   "releaseNotes": "More optimized task fields that allow users to enable any/all of the transformation (XML), variable substitution (JSON and XML) features in a single task instance.</br>Task fails when any of the configured transformation/substitution is NOT applied or when the task is no-op.",
@@ -72,6 +72,14 @@
       "defaultValue": "",
       "groupName": "VariableSubstitution",
       "helpMarkDown": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder. <br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. <br/> Variable Substitution is run after configuration transforms. </br> Note: Only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables."
+    },
+    {
+      "name": "errorOnInvalidSubstitution",
+      "type": "boolean",
+      "label": "Error on empty files and invalid substitution.",
+      "required": false,
+      "defaultValue": false,
+      "helpMarkDown": "If selected, the pipeline fails if the target files are empty or if the substitution fails."
     }
   ],
   "execution": {

Tasks/FileTransformV2/package.json

@@ -17,7 +17,7 @@
   ],
   "version": {
     "Major": 2,
-    "Minor": 252,
+    "Minor": 253,
     "Patch": 0
   },
   "releaseNotes": "ms-resource:loc.releaseNotes",
@@ -72,6 +72,14 @@
       "defaultValue": "",
       "groupName": "VariableSubstitution",
       "helpMarkDown": "ms-resource:loc.input.help.xmlTargetFiles"
+    },
+    {
+      "name": "errorOnInvalidSubstitution",
+      "type": "boolean",
+      "label": "ms-resource:loc.input.label.errorOnInvalidSubstitution",
+      "required": false,
+      "defaultValue": false,
+      "helpMarkDown": "ms-resource:loc.input.help.errorOnInvalidSubstitution"
     }
   ],
   "execution": {