Skip to content

Commit 174ac31

Browse files
Change wording to clarify and correct URI
1 parent cccdd65 commit 174ac31

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/stream-analytics/stream-analytics-cicd-api.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -140,28 +140,28 @@ To publish a Stream Analytics job on IoT Edge, call the POST method using the Ed
140140
|------|-----------|
141141
|POST|`https://management.azure.com/subscriptions/{\**subscriptionid**}/resourceGroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/streamingjobs/{**jobname**}/publishedgepackage?api-version=2017-04-01-preview`|
142142
143-
This asynchronous operation returns a status of 202 until the job has been successfully published. The location response header contains the URI used to get the status of the process. While the process is running, a call to the URI in the location header returns a status of 202. When the process finishes, the URI in the location header returns a status of 200.
143+
The previous call to the Edge Package Publish API triggers an asynchronous operation and returns a status of 202. The **location** response header contains the URI used to get the status of that asynchronous operation. A call to the URI in the **location** header returns a status of 202 to indicate the asynchronous operation is still in progress. When the operation is completed, the call to the URI in the **location** header returns a status of 200.
144144
145145
Example of an Edge package publish call using **curl**:
146146
147147
```bash
148148
curl -d -X POST https://management.azure.com/subscriptions/{subscriptionid}/resourceGroups/{resourcegroupname}/providers/Microsoft.StreamAnalytics/streamingjobs/{jobname}/publishedgepackage?api-version=2017-04-01-preview
149149
```
150150
151-
After making the POST call, you should expect a response with an empty body. Look for the URL located in the HEAD of the response and record it for further use.
152-
153-
Example of the URL from the HEAD of response:
151+
After making the POST call, you should expect a response with an empty body. Look for the URI in the **location** header of the response, and record it for further use.
152+
153+
Example of the URI from the **location** header of response:
154154
155155
```
156-
https://management.azure.com/subscriptions/{**subscriptionid**}/resourcegroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/StreamingJobs/{**resourcename**}/OperationResults/023a4d68-ffaf-4e16-8414-cb6f2e14fe23?api-version=2017-04-01-preview
156+
https://management.azure.com/subscriptions/{**subscriptionid**}/resourcegroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/StreamingJobs/{**resourcename**}/OperationResults/{**guidAssignedToTheAsynchronousOperation**}?api-version=2017-04-01-preview
157157
```
158-
A
159-
Wait for one to two minutes before running the following command to make an API call with the URL you found in the HEAD of the response. Retry the command if you do not get a 200 response.
158+
159+
Wait from a few seconds to a couple of minutes before making a call to the API whose URI you found in the **location** header of the response to the Edge Package Publish API, and repeat the cycle of waiting and retrying until you get a 200 response.
160160
161161
Example of making API call with returned URL with **curl**:
162162
163163
```bash
164-
curl -d –X GET https://management.azure.com/subscriptions/{subscriptionid}/resourceGroups/{resourcegroupname}/providers/Microsoft.StreamAnalytics/streamingjobs/{resourcename}/publishedgepackage?api-version=2017-04-01-preview
164+
curl -d –X GET https://management.azure.com/subscriptions/{**subscriptionid**}/resourcegroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/StreamingJobs/{**resourcename**}/OperationResults/{**guidAssignedToTheAsynchronousOperation**}?api-version=2017-04-01-preview
165165
```
166166
167167
The response includes the information you need to add to the Edge deployment script. The examples below show what information you need to collect and where to add it in the deployment manifest.
@@ -247,11 +247,11 @@ Sample of Deployment Manifest:
247247
}
248248
```
249249
250-
After the configuration of the deployment manifest, refer to [Deploy Azure IoT Edge modules with Azure CLI](../iot-edge/how-to-deploy-modules-cli.md) for deployment.
250+
After having configured the deployment manifest, refer to [Deploy Azure IoT Edge modules with Azure CLI](../iot-edge/how-to-deploy-modules-cli.md) for deployment.
251251
252252
253253
## Next steps
254254
255255
* [Azure Stream Analytics on IoT Edge](stream-analytics-edge.md)
256256
* [ASA on IoT Edge tutorial](../iot-edge/tutorial-deploy-stream-analytics.md)
257-
* [Develop Stream Analytics Edge jobs using Visual Studio tools](stream-analytics-tools-for-visual-studio-edge-jobs.md)
257+
* [Develop Stream Analytics Edge jobs using Visual Studio tools](stream-analytics-tools-for-visual-studio-edge-jobs.md)

0 commit comments

Comments
 (0)