You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,13 @@ For using any credentials like Azure Service Principal in your workflow, add the
54
54
with:
55
55
creds: ${{ secrets.AZURE_CREDENTIALS }}
56
56
```
57
-
57
+
58
+
## Breaking changes
59
+
60
+
All minor versions under `1.1` (e.g., `1.1.x`) will stop working due to a breaking change.
61
+
To ensure continued compatibility, we recommend switching to the `v1` tag, which we will continue to support.
62
+
We are also bumping the minor version to `1.2.1`. If you prefer to pin to a specific version, please update your workflows to use `1.2.1`.
63
+
58
64
## Azure Load Testing Action
59
65
60
66
This section describes the Azure Load Testing GitHub action. You can use this action by referencing `azure/load-testing@v1` action in your workflow. The action runs on Windows, Linux, and Mac runners.
header[UtilModels_1.correlationHeader]=correlationId;// even if we put console.debug its printing along with the logs, so lets just go ahead with the differentiation with azdo, so we can search the timeframe for azdo in correlationid and resource filter.
backOffTimeForRetry+=60;// extra 60 seconds for patch, basically this happens when the service didnot handle some of the external service dependencies, and the external can take time to recover.
throw{message: (err&&err.error&&err.error.message) ? err.error.message : (0,CommonUtils_1.errorCorrection)(httpResponse)};// throwing as message to catch it as err.message
constretrriableCodes=[408,429,500,502,503,504];// 408 - Request Timeout, 429 - Too Many Requests, 500 - Internal Server Error, 502 - Bad Gateway, 503 - Service Unavailable, 504 - Gateway Timeout
21
+
letbackOffTimeForRetry=5;// seconds
22
+
letcorrelationId=`gh-actions-${getUniqueId()}`;
20
23
try{
21
-
letcorrelationId=`gh-actions-${getUniqueId()}`;
22
24
header[correlationHeader]=correlationId;// even if we put console.debug its printing along with the logs, so lets just go ahead with the differentiation with azdo, so we can search the timeframe for azdo in correlationid and resource filter.
backOffTimeForRetry+=60;// extra 60 seconds for patch, basically this happens when the service didnot handle some of the external service dependencies, and the external can take time to recover.
53
+
}
49
54
leterr=awaitgetResultObj(httpResponse);
50
55
throw{message : (err&&err.error&&err.error.message) ? err.error.message : errorCorrection(httpResponse)};// throwing as message to catch it as err.message
0 commit comments