diff --git a/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson b/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson index 6b72c3ef2323..4f1f7a8654bf 100644 --- a/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson +++ b/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson @@ -11,7 +11,7 @@ "loc.input.label.xmlTransformationRules": "Transformation rules", "loc.input.help.xmlTransformationRules": "Provide new line separated list of transformation file rules using the syntax:
-transform -xml ", "loc.input.label.fileType": "File format", - "loc.input.help.fileType": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.help.fileType": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.targetFiles": "Target files", "loc.input.help.targetFiles": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder.", "loc.messages.JSONvariablesubstitutionappliedsuccessfully": "JSON variable substitution applied successfully.", diff --git a/Tasks/FileTransformV1/task.json b/Tasks/FileTransformV1/task.json index 8cb53b4ef12f..c460af9afba5 100644 --- a/Tasks/FileTransformV1/task.json +++ b/Tasks/FileTransformV1/task.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 0 }, "instanceNameFormat": "File Transform: $(Package)", @@ -68,7 +68,7 @@ "EditableOptions": "False" }, "groupName": "VariableSubstitution", - "helpMarkDown": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables." + "helpMarkDown": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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": "targetFiles", diff --git a/Tasks/FileTransformV1/task.loc.json b/Tasks/FileTransformV1/task.loc.json index 67e1e00dccb9..9a88aaf2484d 100644 --- a/Tasks/FileTransformV1/task.loc.json +++ b/Tasks/FileTransformV1/task.loc.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 0 }, "instanceNameFormat": "ms-resource:loc.instanceNameFormat", diff --git a/_generated/FileTransformV1.versionmap.txt b/_generated/FileTransformV1.versionmap.txt index 8cab7f731774..d7a09dd5a8be 100644 --- a/_generated/FileTransformV1.versionmap.txt +++ b/_generated/FileTransformV1.versionmap.txt @@ -1,2 +1,2 @@ -Default|1.231.0 -Node20_229_3|1.231.1 +Default|1.232.0 +Node20_229_3|1.232.1 diff --git a/_generated/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson b/_generated/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson index 6b72c3ef2323..4f1f7a8654bf 100644 --- a/_generated/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson +++ b/_generated/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson @@ -11,7 +11,7 @@ "loc.input.label.xmlTransformationRules": "Transformation rules", "loc.input.help.xmlTransformationRules": "Provide new line separated list of transformation file rules using the syntax:
-transform -xml ", "loc.input.label.fileType": "File format", - "loc.input.help.fileType": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.help.fileType": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.targetFiles": "Target files", "loc.input.help.targetFiles": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder.", "loc.messages.JSONvariablesubstitutionappliedsuccessfully": "JSON variable substitution applied successfully.", diff --git a/_generated/FileTransformV1/task.json b/_generated/FileTransformV1/task.json index 00215deefe3a..3dfe69f95dff 100644 --- a/_generated/FileTransformV1/task.json +++ b/_generated/FileTransformV1/task.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 0 }, "instanceNameFormat": "File Transform: $(Package)", @@ -68,7 +68,7 @@ "EditableOptions": "False" }, "groupName": "VariableSubstitution", - "helpMarkDown": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables." + "helpMarkDown": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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": "targetFiles", @@ -116,7 +116,7 @@ "SkippedUpdatingFile": "Skipped Updating file: %s" }, "_buildConfigMapping": { - "Default": "1.231.0", - "Node20_229_3": "1.231.1" + "Default": "1.232.0", + "Node20_229_3": "1.232.1" } } \ No newline at end of file diff --git a/_generated/FileTransformV1/task.loc.json b/_generated/FileTransformV1/task.loc.json index 63d95aa0438b..a825e1856d65 100644 --- a/_generated/FileTransformV1/task.loc.json +++ b/_generated/FileTransformV1/task.loc.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 0 }, "instanceNameFormat": "ms-resource:loc.instanceNameFormat", @@ -116,7 +116,7 @@ "SkippedUpdatingFile": "ms-resource:loc.messages.SkippedUpdatingFile" }, "_buildConfigMapping": { - "Default": "1.231.0", - "Node20_229_3": "1.231.1" + "Default": "1.232.0", + "Node20_229_3": "1.232.1" } } \ No newline at end of file diff --git a/_generated/FileTransformV1_Node20/Strings/resources.resjson/en-US/resources.resjson b/_generated/FileTransformV1_Node20/Strings/resources.resjson/en-US/resources.resjson index 6b72c3ef2323..4f1f7a8654bf 100644 --- a/_generated/FileTransformV1_Node20/Strings/resources.resjson/en-US/resources.resjson +++ b/_generated/FileTransformV1_Node20/Strings/resources.resjson/en-US/resources.resjson @@ -11,7 +11,7 @@ "loc.input.label.xmlTransformationRules": "Transformation rules", "loc.input.help.xmlTransformationRules": "Provide new line separated list of transformation file rules using the syntax:
-transform -xml ", "loc.input.label.fileType": "File format", - "loc.input.help.fileType": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.help.fileType": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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.targetFiles": "Target files", "loc.input.help.targetFiles": "Provide new line separated list of files to substitute the variable values. Files names are to be provided relative to the root folder.", "loc.messages.JSONvariablesubstitutionappliedsuccessfully": "JSON variable substitution applied successfully.", diff --git a/_generated/FileTransformV1_Node20/task.json b/_generated/FileTransformV1_Node20/task.json index 29a6af2e8ec5..703ec1bcafaf 100644 --- a/_generated/FileTransformV1_Node20/task.json +++ b/_generated/FileTransformV1_Node20/task.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 1 }, "instanceNameFormat": "File Transform: $(Package)", @@ -68,7 +68,7 @@ "EditableOptions": "False" }, "groupName": "VariableSubstitution", - "helpMarkDown": "Provide file format on which substitution has to be perfformed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables." + "helpMarkDown": "Provide file format on which substitution has to be performed
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. Variable Substitution is run after config transforms.
To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions.

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).
{
  \"Data\": {
    \"DefaultConnection\": {
      \"ConnectionString\": \"Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=True\"
    }
  }
}
Variable Substitution is run after configuration transforms.

Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded.
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": "targetFiles", @@ -120,7 +120,7 @@ "SkippedUpdatingFile": "Skipped Updating file: %s" }, "_buildConfigMapping": { - "Default": "1.231.0", - "Node20_229_3": "1.231.1" + "Default": "1.232.0", + "Node20_229_3": "1.232.1" } } \ No newline at end of file diff --git a/_generated/FileTransformV1_Node20/task.loc.json b/_generated/FileTransformV1_Node20/task.loc.json index caf073cb8a78..b9d5d7ccd8a6 100644 --- a/_generated/FileTransformV1_Node20/task.loc.json +++ b/_generated/FileTransformV1_Node20/task.loc.json @@ -17,7 +17,7 @@ ], "version": { "Major": 1, - "Minor": 231, + "Minor": 232, "Patch": 1 }, "instanceNameFormat": "ms-resource:loc.instanceNameFormat", @@ -120,7 +120,7 @@ "SkippedUpdatingFile": "ms-resource:loc.messages.SkippedUpdatingFile" }, "_buildConfigMapping": { - "Default": "1.231.0", - "Node20_229_3": "1.231.1" + "Default": "1.232.0", + "Node20_229_3": "1.232.1" } } \ No newline at end of file