@itentialopensource/adapter-azure_devops 0.2.3 → 0.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/TAB2.md ADDED
@@ -0,0 +1,2165 @@
1
+ # Microsoft Azure DevOps
2
+
3
+ ## Table of Contents
4
+
5
+ - [Getting Started](#getting-started)
6
+ - [Helpful Background Information](#helpful-background-information)
7
+ - [Prerequisites](#prerequisites)
8
+ - [How to Install](#how-to-install)
9
+ - [Testing](#testing)
10
+ - [Configuration](#configuration)
11
+ - [Example Properties](#example-properties)
12
+ - [Connection Properties](#connection-properties)
13
+ - [Authentication Properties](#authentication-properties)
14
+ - [Healthcheck Properties](#healthcheck-properties)
15
+ - [Request Properties](#request-properties)
16
+ - [SSL Properties](#ssl-properties)
17
+ - [Throttle Properties](#throttle-properties)
18
+ - [Proxy Properties](#proxy-properties)
19
+ - [Mongo Properties](#mongo-properties)
20
+ - [Device Broker Properties](#device-broker-properties)
21
+ - [Using this Adapter](#using-this-adapter)
22
+ - [Generic Adapter Calls](#generic-adapter-calls)
23
+ - [Adapter Cache Calls](#adapter-cache-calls)
24
+ - [Adapter Broker Calls](#adapter-broker-calls)
25
+ - [Specific Adapter Calls](#specific-adapter-calls)
26
+ - [Authentication](#authentication)
27
+ - [Additional Information](#additional-information)
28
+ - [Enhancements](#enhancements)
29
+ - [Contributing](#contributing)
30
+ - [Helpful Links](#helpful-links)
31
+ - [Node Scripts](#node-scripts)
32
+ - [Troubleshoot](#troubleshoot)
33
+ - [Connectivity Issues](#connectivity-issues)
34
+ - [Functional Issues](#functional-issues)
35
+
36
+ ## Getting Started
37
+
38
+ These instructions will help you get a copy of the project on your local machine for development and testing. Reading this section is also helpful for deployments as it provides you with pertinent information on prerequisites and properties.
39
+
40
+ ### Helpful Background Information
41
+
42
+ There is <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter documentation available on the Itential Documentation Site</a>. This documentation includes information and examples that are helpful for:
43
+
44
+ ```text
45
+ Authentication
46
+ IAP Service Instance Configuration
47
+ Code Files
48
+ Endpoint Configuration (Action & Schema)
49
+ Mock Data
50
+ Adapter Generic Methods
51
+ Headers
52
+ Security
53
+ Linting and Testing
54
+ Build an Adapter
55
+ Troubleshooting an Adapter
56
+ ```
57
+
58
+ Others will be added over time.
59
+ Want to build a new adapter? Use the <a href="https://adapters.itential.io" target="_blank">Itential Adapter Builder</a>
60
+
61
+ ### Prerequisites
62
+
63
+ The following is a list of required packages for installation on the system the adapter will run on:
64
+
65
+ ```text
66
+ Node.js
67
+ npm
68
+ Git
69
+ ```
70
+
71
+ The following list of packages are required for Itential opensource adapters or custom adapters that have been built utilizing the Itential Adapter Builder. You can install these packages by running npm install inside the adapter directory.
72
+
73
+ <table border="1" class="bordered-table">
74
+ <tr>
75
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Package</span></th>
76
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
77
+ </tr>
78
+ <tr>
79
+ <td style="padding:15px">@itentialopensource/adapter-utils</td>
80
+ <td style="padding:15px">Runtime library classes for all adapters; includes request handling, connection, authentication throttling, and translation.</td>
81
+ </tr>
82
+ <tr>
83
+ <td style="padding:15px">ajv</td>
84
+ <td style="padding:15px">Required for validation of adapter properties to integrate with Azure_devops.</td>
85
+ </tr>
86
+ <tr>
87
+ <td style="padding:15px">axios</td>
88
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
89
+ </tr>
90
+ <tr>
91
+ <td style="padding:15px">commander</td>
92
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
93
+ </tr>
94
+ <tr>
95
+ <td style="padding:15px">dns-lookup-promise</td>
96
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
97
+ </tr>
98
+ <tr>
99
+ <td style="padding:15px">fs-extra</td>
100
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
101
+ </tr>
102
+ <tr>
103
+ <td style="padding:15px">mocha</td>
104
+ <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
105
+ </tr>
106
+ <tr>
107
+ <td style="padding:15px">mocha-param</td>
108
+ <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
109
+ </tr>
110
+ <tr>
111
+ <td style="padding:15px">mongodb</td>
112
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
113
+ </tr>
114
+ <tr>
115
+ <td style="padding:15px">nyc</td>
116
+ <td style="padding:15px">Testing coverage library that is utilized by some of the node scripts that are included with the adapter.</td>
117
+ </tr>
118
+ <tr>
119
+ <td style="padding:15px">ping</td>
120
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
121
+ </tr>
122
+ <tr>
123
+ <td style="padding:15px">readline-sync</td>
124
+ <td style="padding:15px">Utilized by the node script that comes with the adapter; helps to test unit and integration functionality.</td>
125
+ </tr>
126
+ <tr>
127
+ <td style="padding:15px">semver</td>
128
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
129
+ </tr>
130
+ <tr>
131
+ <td style="padding:15px">winston</td>
132
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
133
+ </tr>
134
+ </table>
135
+ <br>
136
+
137
+ If you are developing and testing a custom adapter, or have testing capabilities on an Itential opensource adapter, you will need to install these packages as well.
138
+
139
+ ```text
140
+ chai
141
+ eslint
142
+ eslint-config-airbnb-base
143
+ eslint-plugin-import
144
+ eslint-plugin-json
145
+ testdouble
146
+ ```
147
+
148
+ ### How to Install
149
+
150
+ 1. Set up the name space location in your IAP node_modules.
151
+
152
+ ```bash
153
+ cd /opt/pronghorn/current/node_modules (* could be in a different place)
154
+ if the @itentialopensource directory does not exist, create it:
155
+ mkdir @itentialopensource
156
+ ```
157
+
158
+ 2. Clone/unzip/tar the adapter into your IAP environment.
159
+
160
+ ```bash
161
+ cd \@itentialopensource
162
+ git clone git@gitlab.com:\@itentialopensource/adapters/adapter-azure_devops
163
+ or
164
+ unzip adapter-azure_devops.zip
165
+ or
166
+ tar -xvf adapter-azure_devops.tar
167
+ ```
168
+
169
+ 3. Run the adapter install script.
170
+
171
+ ```bash
172
+ cd adapter-azure_devops
173
+ npm install
174
+ npm run lint:errors
175
+ npm run test
176
+ ```
177
+
178
+ 4. Restart IAP
179
+
180
+ ```bash
181
+ systemctl restart pronghorn
182
+ ```
183
+
184
+ 5. Create an adapter service instance configuration in IAP Admin Essentials GUI
185
+
186
+ 6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
187
+
188
+ 7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
189
+
190
+
191
+ For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
192
+
193
+ 3. Install adapter dependencies and check the adapter.
194
+
195
+ ```bash
196
+ cd adapter-azure_devops
197
+ npm run adapter:install
198
+ ```
199
+
200
+ 4. Restart IAP
201
+
202
+ ```bash
203
+ systemctl restart pronghorn
204
+ ```
205
+
206
+ 5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
207
+
208
+
209
+ ### Testing
210
+
211
+ Mocha is generally used to test all Itential Opensource Adapters. There are unit tests as well as integration tests performed. Integration tests can generally be run as standalone using mock data and running the adapter in stub mode, or as integrated. When running integrated, every effort is made to prevent environmental failures, however there is still a possibility.
212
+
213
+ #### Unit Testing
214
+
215
+ Unit Testing includes testing basic adapter functionality as well as error conditions that are triggered in the adapter prior to any integration. There are two ways to run unit tests. The prefered method is to use the testRunner script; however, both methods are provided here.
216
+
217
+ ```bash
218
+ node utils/testRunner --unit
219
+
220
+ npm run test:unit
221
+ npm run test:baseunit
222
+ ```
223
+
224
+ To add new unit tests, edit the `test/unit/adapterTestUnit.js` file. The tests that are already in this file should provide guidance for adding additional tests.
225
+
226
+ #### Integration Testing - Standalone
227
+
228
+ Standalone Integration Testing requires mock data to be provided with the entities. If this data is not provided, standalone integration testing will fail. When the adapter is set to run in stub mode (setting the stub property to true), the adapter will run through its code up to the point of making the request. It will then retrieve the mock data and return that as if it had received that data as the response from Azure_devops. It will then translate the data so that the adapter can return the expected response to the rest of the Itential software. Standalone is the default integration test.
229
+
230
+ Similar to unit testing, there are two ways to run integration tests. Using the testRunner script is better because it prevents you from having to edit the test script; it will also resets information after testing is complete so that credentials are not saved in the file.
231
+
232
+ ```bash
233
+ node utils/testRunner
234
+ answer no at the first prompt
235
+
236
+ npm run test:integration
237
+ ```
238
+
239
+ To add new integration tests, edit the `test/integration/adapterTestIntegration.js` file. The tests that are already in this file should provide guidance for adding additional tests.
240
+
241
+ #### Integration Testing
242
+
243
+ Integration Testing requires connectivity to Azure_devops. By using the testRunner script it prevents you from having to edit the integration test. It also resets the integration test after the test is complete so that credentials are not saved in the file.
244
+
245
+ > **Note**: These tests have been written as a best effort to make them work in most environments. However, the Adapter Builder often does not have the necessary information that is required to set up valid integration tests. For example, the order of the requests can be very important and data is often required for `creates` and `updates`. Hence, integration tests may have to be enhanced before they will work (integrate) with Azure_devops. Even after tests have been set up properly, it is possible there are environmental constraints that could result in test failures. Some examples of possible environmental issues are customizations that have been made within Azure_devops which change order dependencies or required data.
246
+
247
+ ```bash
248
+ node utils/testRunner
249
+ answer yes at the first prompt
250
+ answer all other questions on connectivity and credentials
251
+ ```
252
+
253
+ Test should also be written to clean up after themselves. However, it is important to understand that in some cases this may not be possible. In addition, whenever exceptions occur, test execution may be stopped, which will prevent cleanup actions from running. It is recommended that tests be utilized in dev and test labs only.
254
+
255
+ > **Reminder**: Do not check in code with actual credentials to systems.
256
+
257
+ ## Configuration
258
+
259
+ This section defines **all** the properties that are available for the adapter, including detailed information on what each property is for. If you are not using certain capabilities with this adapter, you do not need to define all of the properties. An example of how the properties for this adapter can be used with tests or IAP are provided in the sampleProperties.
260
+
261
+ ### Example Properties
262
+
263
+ ```json
264
+ "properties": {
265
+ "host": "dev.azure.com",
266
+ "port": 443,
267
+ "choosepath": "",
268
+ "base_path": "/",
269
+ "version": "",
270
+ "cache_location": "none",
271
+ "encode_pathvars": true,
272
+ "encode_queryvars": true,
273
+ "save_metric": false,
274
+ "stub": true,
275
+ "protocol": "https",
276
+ "authentication": {
277
+ "auth_method": "static_token",
278
+ "username": "username",
279
+ "password": "password",
280
+ "token": "token",
281
+ "token_timeout": 600000,
282
+ "token_cache": "local",
283
+ "invalid_token_error": 401,
284
+ "auth_field": "header.headers.Authorization",
285
+ "auth_field_format": "Basic {b64}Basic:{token}{/b64}",
286
+ "auth_logging": false,
287
+ "client_id": "",
288
+ "client_secret": "",
289
+ "grant_type": "",
290
+ "sensitive": [],
291
+ "sso": {
292
+ "protocol": "",
293
+ "host": "",
294
+ "port": 0
295
+ },
296
+ "multiStepAuthCalls": [
297
+ {
298
+ "name": "",
299
+ "requestFields": {},
300
+ "responseFields": {},
301
+ "successfullResponseCode": 200
302
+ }
303
+ ]
304
+ },
305
+ "healthcheck": {
306
+ "type": "none",
307
+ "frequency": 60000,
308
+ "query_object": {},
309
+ "addlHeaders": {}
310
+ },
311
+ "throttle": {
312
+ "throttle_enabled": false,
313
+ "number_pronghorns": 1,
314
+ "sync_async": "sync",
315
+ "max_in_queue": 1000,
316
+ "concurrent_max": 1,
317
+ "expire_timeout": 0,
318
+ "avg_runtime": 200,
319
+ "priorities": [
320
+ {
321
+ "value": 0,
322
+ "percent": 100
323
+ }
324
+ ]
325
+ },
326
+ "request": {
327
+ "number_redirects": 0,
328
+ "number_retries": 3,
329
+ "limit_retry_error": [
330
+ 0
331
+ ],
332
+ "failover_codes": [],
333
+ "attempt_timeout": 5000,
334
+ "global_request": {
335
+ "payload": {},
336
+ "uriOptions": {},
337
+ "addlHeaders": {},
338
+ "authData": {}
339
+ },
340
+ "healthcheck_on_timeout": true,
341
+ "return_raw": false,
342
+ "archiving": false,
343
+ "return_request": false
344
+ },
345
+ "proxy": {
346
+ "enabled": false,
347
+ "host": "",
348
+ "port": 1,
349
+ "protocol": "http",
350
+ "username": "",
351
+ "password": ""
352
+ },
353
+ "ssl": {
354
+ "ecdhCurve": "",
355
+ "enabled": false,
356
+ "accept_invalid_cert": false,
357
+ "ca_file": "",
358
+ "key_file": "",
359
+ "cert_file": "",
360
+ "secure_protocol": "",
361
+ "ciphers": ""
362
+ },
363
+ "mongo": {
364
+ "host": "",
365
+ "port": 0,
366
+ "database": "",
367
+ "username": "",
368
+ "password": "",
369
+ "replSet": "",
370
+ "db_ssl": {
371
+ "enabled": false,
372
+ "accept_invalid_cert": false,
373
+ "ca_file": "",
374
+ "key_file": "",
375
+ "cert_file": ""
376
+ }
377
+ },
378
+ "devicebroker": {
379
+ "getDevice": [
380
+ {
381
+ "path": "/get/devices/{id}",
382
+ "method": "GET",
383
+ "query": {},
384
+ "body": {},
385
+ "headers": {},
386
+ "handleFailure": "ignore",
387
+ "requestFields": {
388
+ "id": "name"
389
+ },
390
+ "responseDatakey": "",
391
+ "responseFields": {
392
+ "name": "host",
393
+ "ostype": "os",
394
+ "ostypePrefix": "system-",
395
+ "ipaddress": "attributes.ipaddr",
396
+ "port": "443"
397
+ }
398
+ }
399
+ ],
400
+ "getDevicesFiltered": [
401
+ {
402
+ "path": "/get/devices",
403
+ "method": "GET",
404
+ "pagination": {
405
+ "offsetVar": "",
406
+ "limitVar": "",
407
+ "incrementBy": "limit",
408
+ "requestLocation": "query"
409
+ },
410
+ "query": {},
411
+ "body": {},
412
+ "headers": {},
413
+ "handleFailure": "ignore",
414
+ "requestFields": {},
415
+ "responseDatakey": "",
416
+ "responseFields": {
417
+ "name": "host",
418
+ "ostype": "os",
419
+ "ostypePrefix": "system-",
420
+ "ipaddress": "attributes.ipaddr",
421
+ "port": "443"
422
+ }
423
+ }
424
+ ],
425
+ "isAlive": [
426
+ {
427
+ "path": "/get/devices/{id}/status",
428
+ "method": "GET",
429
+ "query": {},
430
+ "body": {},
431
+ "headers": {},
432
+ "handleFailure": "ignore",
433
+ "requestFields": {
434
+ "id": "name"
435
+ },
436
+ "responseDatakey": "",
437
+ "responseFields": {
438
+ "status": "status",
439
+ "statusValue": "online"
440
+ }
441
+ }
442
+ ],
443
+ "getConfig": [
444
+ {
445
+ "path": "/get/devices/{id}/configPart1",
446
+ "method": "GET",
447
+ "query": {},
448
+ "body": {},
449
+ "headers": {},
450
+ "handleFailure": "ignore",
451
+ "requestFields": {
452
+ "id": "name"
453
+ },
454
+ "responseDatakey": "",
455
+ "responseFields": {}
456
+ }
457
+ ],
458
+ "getCount": [
459
+ {
460
+ "path": "/get/devices",
461
+ "method": "GET",
462
+ "query": {},
463
+ "body": {},
464
+ "headers": {},
465
+ "handleFailure": "ignore",
466
+ "requestFields": {},
467
+ "responseDatakey": "",
468
+ "responseFields": {}
469
+ }
470
+ ]
471
+ },
472
+ "cache": {
473
+ "enabled": false,
474
+ "entities": [
475
+ {
476
+ "entityType": "",
477
+ "frequency": 1440,
478
+ "flushOnFail": false,
479
+ "limit": 1000,
480
+ "retryAttempts": 5,
481
+ "sort": true,
482
+ "populate": [
483
+ {
484
+ "path": "",
485
+ "method": "GET",
486
+ "pagination": {
487
+ "offsetVar": "",
488
+ "limitVar": "",
489
+ "incrementBy": "limit",
490
+ "requestLocation": "query"
491
+ },
492
+ "query": {},
493
+ "body": {},
494
+ "headers": {},
495
+ "handleFailure": "ignore",
496
+ "requestFields": {},
497
+ "responseDatakey": "",
498
+ "responseFields": {}
499
+ }
500
+ ],
501
+ "cachedTasks": [
502
+ {
503
+ "name": "",
504
+ "filterField": "",
505
+ "filterLoc": ""
506
+ }
507
+ ]
508
+ }
509
+ ]
510
+ }
511
+ }
512
+ ```
513
+
514
+ ### Connection Properties
515
+
516
+ These base properties are used to connect to Azure_devops upon the adapter initially coming up. It is important to set these properties appropriately.
517
+
518
+ <table border="1" class="bordered-table">
519
+ <tr>
520
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
521
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
522
+ </tr>
523
+ <tr>
524
+ <td style="padding:15px">host</td>
525
+ <td style="padding:15px">Required. A fully qualified domain name or IP address.</td>
526
+ </tr>
527
+ <tr>
528
+ <td style="padding:15px">port</td>
529
+ <td style="padding:15px">Required. Used to connect to the server.</td>
530
+ </tr>
531
+ <tr>
532
+ <td style="padding:15px">base_path</td>
533
+ <td style="padding:15px">Optional. Used to define part of a path that is consistent for all or most endpoints. It makes the URIs easier to use and maintain but can be overridden on individual calls. An example **base_path** might be `/rest/api`. Default is ``.</td>
534
+ </tr>
535
+ <tr>
536
+ <td style="padding:15px">version</td>
537
+ <td style="padding:15px">Optional. Used to set a global version for action endpoints. This makes it faster to update the adapter when endpoints change. As with the base-path, version can be overridden on individual endpoints. Default is ``.</td>
538
+ </tr>
539
+ <tr>
540
+ <td style="padding:15px">cache_location</td>
541
+ <td style="padding:15px">Optional. Used to define where the adapter cache is located. The cache is used to maintain an entity list to improve performance. Storage locally is lost when the adapter is restarted. Storage in Redis is preserved upon adapter restart. Default is none which means no caching of the entity list.</td>
542
+ </tr>
543
+ <tr>
544
+ <td style="padding:15px">encode_pathvars</td>
545
+ <td style="padding:15px">Optional. Used to tell the adapter to encode path variables or not. The default behavior is to encode them so this property can be used to stop that behavior.</td>
546
+ </tr>
547
+ <tr>
548
+ <td style="padding:15px">encode_queryvars</td>
549
+ <td style="padding:15px">Optional. Used to tell the adapter to encode query parameters or not. The default behavior is to encode them so this property can be used to stop that behavior.</td>
550
+ </tr>
551
+ <tr>
552
+ <td style="padding:15px">save_metric</td>
553
+ <td style="padding:15px">Optional. Used to tell the adapter to save metric information (this does not impact metrics returned on calls). This allows the adapter to gather metrics over time. Metric data can be stored in a database or on the file system.</td>
554
+ </tr>
555
+ <tr>
556
+ <td style="padding:15px">stub</td>
557
+ <td style="padding:15px">Optional. Indicates whether the stub should run instead of making calls to Azure_devops (very useful during basic testing). Default is false (which means connect to Azure_devops).</td>
558
+ </tr>
559
+ <tr>
560
+ <td style="padding:15px">protocol</td>
561
+ <td style="padding:15px">Optional. Notifies the adapter whether to use HTTP or HTTPS. Default is HTTP.</td>
562
+ </tr>
563
+ </table>
564
+ <br>
565
+
566
+ A connectivity check tells IAP the adapter has loaded successfully.
567
+
568
+ ### Authentication Properties
569
+
570
+ The following properties are used to define the authentication process to Azure_devops.
571
+
572
+ >**Note**: Depending on the method that is used to authenticate with Azure_devops, you may not need to set all of the authentication properties.
573
+
574
+ <table border="1" class="bordered-table">
575
+ <tr>
576
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
577
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
578
+ </tr>
579
+ <tr>
580
+ <td style="padding:15px">auth_method</td>
581
+ <td style="padding:15px">Required. Used to define the type of authentication currently supported. Authentication methods currently supported are: `basic user_password`, `static_token`, `request_token`, and `no_authentication`.</td>
582
+ </tr>
583
+ <tr>
584
+ <td style="padding:15px">username</td>
585
+ <td style="padding:15px">Used to authenticate with Azure_devops on every request or when pulling a token that will be used in subsequent requests.</td>
586
+ </tr>
587
+ <tr>
588
+ <td style="padding:15px">password</td>
589
+ <td style="padding:15px">Used to authenticate with Azure_devops on every request or when pulling a token that will be used in subsequent requests.</td>
590
+ </tr>
591
+ <tr>
592
+ <td style="padding:15px">token</td>
593
+ <td style="padding:15px">Defines a static token that can be used on all requests. Only used with `static_token` as an authentication method (auth\_method).</td>
594
+ </tr>
595
+ <tr>
596
+ <td style="padding:15px">invalid_token_error</td>
597
+ <td style="padding:15px">Defines the HTTP error that is received when the token is invalid. Notifies the adapter to pull a new token and retry the request. Default is 401.</td>
598
+ </tr>
599
+ <tr>
600
+ <td style="padding:15px">token_timeout</td>
601
+ <td style="padding:15px">Defines how long a token is valid. Measured in milliseconds. Once a dynamic token is no longer valid, the adapter has to pull a new token. If the token_timeout is set to -1, the adapter will pull a token on every request to Azure_devops. If the timeout_token is 0, the adapter will use the expiration from the token response to determine when the token is no longer valid.</td>
602
+ </tr>
603
+ <tr>
604
+ <td style="padding:15px">token_cache</td>
605
+ <td style="padding:15px">Used to determine where the token should be stored (local memory or in Redis).</td>
606
+ </tr>
607
+ <tr>
608
+ <td style="padding:15px">auth_field</td>
609
+ <td style="padding:15px">Defines the request field the authentication (e.g., token are basic auth credentials) needs to be placed in order for the calls to work.</td>
610
+ </tr>
611
+ <tr>
612
+ <td style="padding:15px">auth_field_format</td>
613
+ <td style="padding:15px">Defines the format of the auth\_field. See examples below. Items enclosed in {} inform the adapter to perofrm an action prior to sending the data. It may be to replace the item with a value or it may be to encode the item.</td>
614
+ </tr>
615
+ <tr>
616
+ <td style="padding:15px">auth_logging</td>
617
+ <td style="padding:15px">Setting this true will add some additional logs but this should only be done when trying to debug an issue as certain credential information may be logged out when this is true.</td>
618
+ </tr>
619
+ <tr>
620
+ <td style="padding:15px">client_id</td>
621
+ <td style="padding:15px">Provide a client id when needed, this is common on some types of OAuth.</td>
622
+ </tr>
623
+ <tr>
624
+ <td style="padding:15px">client_secret</td>
625
+ <td style="padding:15px">Provide a client secret when needed, this is common on some types of OAuth.</td>
626
+ </tr>
627
+ <tr>
628
+ <td style="padding:15px">grant_type</td>
629
+ <td style="padding:15px">Provide a grant type when needed, this is common on some types of OAuth.</td>
630
+ </tr>
631
+ </table>
632
+ <br>
633
+
634
+ #### Examples of authentication field format
635
+
636
+ ```json
637
+ "{token}"
638
+ "Token {token}"
639
+ "{username}:{password}"
640
+ "Basic {b64}{username}:{password}{/b64}"
641
+ ```
642
+
643
+ ### Healthcheck Properties
644
+
645
+ The healthcheck properties defines the API that runs the healthcheck to tell the adapter that it can reach Azure_devops. There are currently three types of healthchecks.
646
+
647
+ - None - Not recommended. Adapter will not run a healthcheck. Consequently, unable to determine before making a request if the adapter can reach Azure_devops.
648
+ - Startup - Adapter will check for connectivity when the adapter initially comes up, but it will not check afterwards.
649
+ - Intermittent - Adapter will check connectivity to Azure_devops at a frequency defined in the `frequency` property.
650
+
651
+ <table border="1" class="bordered-table">
652
+ <tr>
653
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
654
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
655
+ </tr>
656
+ <tr>
657
+ <td style="padding:15px">type</td>
658
+ <td style="padding:15px">Required. The type of health check to run.</td>
659
+ </tr>
660
+ <tr>
661
+ <td style="padding:15px">frequency</td>
662
+ <td style="padding:15px">Required if intermittent. Defines how often the health check should run. Measured in milliseconds. Default is 300000.</td>
663
+ </tr>
664
+ <tr>
665
+ <td style="padding:15px">query_object</td>
666
+ <td style="padding:15px">Query parameters to be added to the adapter healthcheck call.</td>
667
+ </tr>
668
+ </table>
669
+ <br>
670
+
671
+ ### Request Properties
672
+
673
+ The request section defines properties to help handle requests.
674
+
675
+ <table border="1" class="bordered-table">
676
+ <tr>
677
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
678
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
679
+ </tr>
680
+ <tr>
681
+ <td style="padding:15px">number_redirects</td>
682
+ <td style="padding:15px">Optional. Tells the adapter that the request may be redirected and gives it a maximum number of redirects to allow before returning an error. Default is 0 - no redirects.</td>
683
+ </tr>
684
+ <tr>
685
+ <td style="padding:15px">number_retries</td>
686
+ <td style="padding:15px">Tells the adapter how many times to retry a request that has either aborted or reached a limit error before giving up and returning an error.</td>
687
+ </tr>
688
+ <tr>
689
+ <td style="padding:15px">limit_retry_error</td>
690
+ <td style="padding:15px">Optional. Can be either an integer or an array. Indicates the http error status number to define that no capacity was available and, after waiting a short interval, the adapter can retry the request. If an array is provvided, the array can contain integers or strings. Strings in the array are used to define ranges (e.g. "502-506"). Default is [0].</td>
691
+ </tr>
692
+ <tr>
693
+ <td style="padding:15px">failover_codes</td>
694
+ <td style="padding:15px">An array of error codes for which the adapter will send back a failover flag to IAP so that the Platform can attempt the action in another adapter.</td>
695
+ </tr>
696
+ <tr>
697
+ <td style="padding:15px">attempt_timeout</td>
698
+ <td style="padding:15px">Optional. Tells how long the adapter should wait before aborting the attempt. On abort, the adapter will do one of two things: 1) return the error; or 2) if **healthcheck\_on\_timeout** is set to true, it will abort the request and run a Healthcheck until it re-establishes connectivity to Azure_devops, and then will re-attempt the request that aborted. Default is 5000 milliseconds.</td>
699
+ </tr>
700
+ <tr>
701
+ <td style="padding:15px">global_request</td>
702
+ <td style="padding:15px">Optional. This is information that the adapter can include in all requests to the other system. This is easier to define and maintain than adding this information in either the code (adapter.js) or the action files.</td>
703
+ </tr>
704
+ <tr>
705
+ <td style="padding:15px">global_request -> payload</td>
706
+ <td style="padding:15px">Optional. Defines any information that should be included on all requests sent to the other system that have a payload/body.</td>
707
+ </tr>
708
+ <tr>
709
+ <td style="padding:15px">global_request -> uriOptions</td>
710
+ <td style="padding:15px">Optional. Defines any information that should be sent as untranslated query options (e.g. page, size) on all requests to the other system.</td>
711
+ </tr>
712
+ <tr>
713
+ <td style="padding:15px">global_request -> addlHeaders</td>
714
+ <td style="padding:15px">Optioonal. Defines any headers that should be sent on all requests to the other system.</td>
715
+ </tr>
716
+ <tr>
717
+ <td style="padding:15px">global_request -> authData</td>
718
+ <td style="padding:15px">Optional. Defines any additional authentication data used to authentice with the other system. This authData needs to be consistent on every request.</td>
719
+ </tr>
720
+ <tr>
721
+ <td style="padding:15px">healthcheck_on_timeout</td>
722
+ <td style="padding:15px">Required. Defines if the adapter should run a health check on timeout. If set to true, the adapter will abort the request and run a health check until it re-establishes connectivity and then it will re-attempt the request.</td>
723
+ </tr>
724
+ <tr>
725
+ <td style="padding:15px">return_raw</td>
726
+ <td style="padding:15px">Optional. Tells the adapter whether the raw response should be returned as well as the IAP response. This is helpful when running integration tests to save mock data. It does add overhead to the response object so it is not ideal from production.</td>
727
+ </tr>
728
+ <tr>
729
+ <td style="padding:15px">archiving</td>
730
+ <td style="padding:15px">Optional flag. Default is false. It archives the request, the results and the various times (wait time, Azure_devops time and overall time) in the `adapterid_results` collection in MongoDB. Although archiving might be desirable, be sure to develop a strategy before enabling this capability. Consider how much to archive and what strategy to use for cleaning up the collection in the database so that it does not become too large, especially if the responses are large.</td>
731
+ </tr>
732
+ <tr>
733
+ <td style="padding:15px">return_request</td>
734
+ <td style="padding:15px">Optional flag. Default is false. Will return the actual request that is made including headers. This should only be used during debugging issues as there could be credentials in the actual request.</td>
735
+ </tr>
736
+ </table>
737
+ <br>
738
+
739
+ ### SSL Properties
740
+
741
+ The SSL section defines the properties utilized for ssl authentication with Azure_devops. SSL can work two different ways: set the `accept\_invalid\_certs` flag to true (only recommended for lab environments), or provide a `ca\_file`.
742
+
743
+ <table border="1" class="bordered-table">
744
+ <tr>
745
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
746
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
747
+ </tr>
748
+ <tr>
749
+ <td style="padding:15px">enabled</td>
750
+ <td style="padding:15px">If SSL is required, set to true.</td>
751
+ </tr>
752
+ <tr>
753
+ <td style="padding:15px">accept_invalid_certs</td>
754
+ <td style="padding:15px">Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false.</td>
755
+ </tr>
756
+ <tr>
757
+ <td style="padding:15px">ca_file</td>
758
+ <td style="padding:15px">Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required.</td>
759
+ </tr>
760
+ <tr>
761
+ <td style="padding:15px">key_file</td>
762
+ <td style="padding:15px">Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL.</td>
763
+ </tr>
764
+ <tr>
765
+ <td style="padding:15px">cert_file</td>
766
+ <td style="padding:15px">Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL.</td>
767
+ </tr>
768
+ <tr>
769
+ <td style="padding:15px">secure_protocol</td>
770
+ <td style="padding:15px">Defines the protocol (e.g., SSLv3_method) to use on the SSL request.</td>
771
+ </tr>
772
+ <tr>
773
+ <td style="padding:15px">ciphers</td>
774
+ <td style="padding:15px">Required if SSL enabled. Specifies a list of SSL ciphers to use.</td>
775
+ </tr>
776
+ <tr>
777
+ <td style="padding:15px">ecdhCurve</td>
778
+ <td style="padding:15px">During testing on some Node 8 environments, you need to set `ecdhCurve` to auto. If you do not, you will receive PROTO errors when attempting the calls. This is the only usage of this property and to our knowledge it only impacts Node 8 and 9.</td>
779
+ </tr>
780
+ </table>
781
+ <br>
782
+
783
+ ### Throttle Properties
784
+
785
+ The throttle section is used when requests to Azure_devops must be queued (throttled). All of the properties in this section are optional.
786
+
787
+ <table border="1" class="bordered-table">
788
+ <tr>
789
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
790
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
791
+ </tr>
792
+ <tr>
793
+ <td style="padding:15px">throttle_enabled</td>
794
+ <td style="padding:15px">Default is false. Defines if the adapter should use throttling or not.</td>
795
+ </tr>
796
+ <tr>
797
+ <td style="padding:15px">number_pronghorns</td>
798
+ <td style="padding:15px">Default is 1. Defines if throttling is done in a single Itential instance or whether requests are being throttled across multiple Itential instances (minimum = 1, maximum = 20). Throttling in a single Itential instance uses an in-memory queue so there is less overhead. Throttling across multiple Itential instances requires placing the request and queue information into a shared resource (e.g. database) so that each instance can determine what is running and what is next to run. Throttling across multiple instances requires additional I/O overhead.</td>
799
+ </tr>
800
+ <tr>
801
+ <td style="padding:15px">sync-async</td>
802
+ <td style="padding:15px">This property is not used at the current time (it is for future expansion of the throttling engine).</td>
803
+ </tr>
804
+ <tr>
805
+ <td style="padding:15px">max_in_queue</td>
806
+ <td style="padding:15px">Represents the maximum number of requests the adapter should allow into the queue before rejecting requests (minimum = 1, maximum = 5000). This is not a limit on what the adapter can handle but more about timely responses to requests. The default is currently 1000.</td>
807
+ </tr>
808
+ <tr>
809
+ <td style="padding:15px">concurrent_max</td>
810
+ <td style="padding:15px">Defines the number of requests the adapter can send to Azure_devops at one time (minimum = 1, maximum = 1000). The default is 1 meaning each request must be sent to Azure_devops in a serial manner.</td>
811
+ </tr>
812
+ <tr>
813
+ <td style="padding:15px">expire_timeout</td>
814
+ <td style="padding:15px">Default is 0. Defines a graceful timeout of the request session. After a request has completed, the adapter will wait additional time prior to sending the next request. Measured in milliseconds (minimum = 0, maximum = 60000).</td>
815
+ </tr>
816
+ <tr>
817
+ <td style="padding:15px">average_runtime</td>
818
+ <td style="padding:15px">Represents the approximate average of how long it takes Azure_devops to handle each request. Measured in milliseconds (minimum = 50, maximum = 60000). Default is 200. This metric has performance implications. If the runtime number is set too low, it puts extra burden on the CPU and memory as the requests will continually try to run. If the runtime number is set too high, requests may wait longer than they need to before running. The number does not need to be exact but your throttling strategy depends heavily on this number being within reason. If averages range from 50 to 250 milliseconds you might pick an average run-time somewhere in the middle so that when Azure_devops performance is exceptional you might run a little slower than you might like, but when it is poor you still run efficiently.</td>
819
+ </tr>
820
+ <tr>
821
+ <td style="padding:15px">priorities</td>
822
+ <td style="padding:15px">An array of priorities and how to handle them in relation to the throttle queue. Array of objects that include priority value and percent of queue to put the item ex { value: 1, percent: 10 }</td>
823
+ </tr>
824
+ </table>
825
+ <br>
826
+
827
+ ### Proxy Properties
828
+
829
+ The proxy section defines the properties to utilize when Azure_devops is behind a proxy server.
830
+
831
+ <table border="1" class="bordered-table">
832
+ <tr>
833
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
834
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
835
+ </tr>
836
+ <tr>
837
+ <td style="padding:15px">enabled</td>
838
+ <td style="padding:15px">Required. Default is false. If Azure_devops is behind a proxy server, set enabled flag to true.</td>
839
+ </tr>
840
+ <tr>
841
+ <td style="padding:15px">host</td>
842
+ <td style="padding:15px">Host information for the proxy server. Required if `enabled` is true.</td>
843
+ </tr>
844
+ <tr>
845
+ <td style="padding:15px">port</td>
846
+ <td style="padding:15px">Port information for the proxy server. Required if `enabled` is true.</td>
847
+ </tr>
848
+ <tr>
849
+ <td style="padding:15px">protocol</td>
850
+ <td style="padding:15px">The protocol (i.e., http, https, etc.) used to connect to the proxy. Default is http.</td>
851
+ </tr>
852
+ <tr>
853
+ <td style="padding:15px">username</td>
854
+ <td style="padding:15px">If there is authentication for the proxy, provide the username here.</td>
855
+ </tr>
856
+ <tr>
857
+ <td style="padding:15px">password</td>
858
+ <td style="padding:15px">If there is authentication for the proxy, provide the password here.</td>
859
+ </tr>
860
+ </table>
861
+ <br>
862
+
863
+ ### Mongo Properties
864
+
865
+ The mongo section defines the properties used to connect to a Mongo database. Mongo can be used for throttling as well as to persist metric data. If not provided, metrics will be stored in the file system.
866
+
867
+ <table border="1" class="bordered-table">
868
+ <tr>
869
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
870
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
871
+ </tr>
872
+ <tr>
873
+ <td style="padding:15px">host</td>
874
+ <td style="padding:15px">Optional. Host information for the mongo server.</td>
875
+ </tr>
876
+ <tr>
877
+ <td style="padding:15px">port</td>
878
+ <td style="padding:15px">Optional. Port information for the mongo server.</td>
879
+ </tr>
880
+ <tr>
881
+ <td style="padding:15px">database</td>
882
+ <td style="padding:15px">Optional. The database for the adapter to use for its data.</td>
883
+ </tr>
884
+ <tr>
885
+ <td style="padding:15px">username</td>
886
+ <td style="padding:15px">Optional. If credentials are required to access mongo, this is the user to login as.</td>
887
+ </tr>
888
+ <tr>
889
+ <td style="padding:15px">password</td>
890
+ <td style="padding:15px">Optional. If credentials are required to access mongo, this is the password to login with.</td>
891
+ </tr>
892
+ <tr>
893
+ <td style="padding:15px">replSet</td>
894
+ <td style="padding:15px">Optional. If the database is set up to use replica sets, define it here so it can be added to the database connection.</td>
895
+ </tr>
896
+ <tr>
897
+ <td style="padding:15px">db_ssl</td>
898
+ <td style="padding:15px">Optional. Contains information for SSL connectivity to the database.</td>
899
+ </tr>
900
+ <tr>
901
+ <td style="padding:15px">db_ssl -> enabled</td>
902
+ <td style="padding:15px">If SSL is required, set to true.</td>
903
+ </tr>
904
+ <tr>
905
+ <td style="padding:15px">db_ssl -> accept_invalid_cert</td>
906
+ <td style="padding:15px">Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false.</td>
907
+ </tr>
908
+ <tr>
909
+ <td style="padding:15px">db_ssl -> ca_file</td>
910
+ <td style="padding:15px">Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required.</td>
911
+ </tr>
912
+ <tr>
913
+ <td style="padding:15px">db_ssl -> key_file</td>
914
+ <td style="padding:15px">Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL.</td>
915
+ </tr>
916
+ <tr>
917
+ <td style="padding:15px">db_ssl -> cert_file</td>
918
+ <td style="padding:15px">Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL.</td>
919
+ </tr>
920
+ </table>
921
+ <br>
922
+
923
+ ### Device Broker Properties
924
+
925
+ The device broker section defines the properties used integrate Azure_devops to the device broker. Each broker call is represented and has an array of calls that can be used to build the response. This describes the calls and then the fields which are available in the calls.
926
+
927
+ <table border="1" class="bordered-table">
928
+ <tr>
929
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
930
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
931
+ </tr>
932
+ <tr>
933
+ <td style="padding:15px">getDevice</td>
934
+ <td style="padding:15px">The array of calls used to get device details for the broker</td>
935
+ </tr>
936
+ <tr>
937
+ <td style="padding:15px">getDevicesFiltered</td>
938
+ <td style="padding:15px">The array of calls used to get devices for the broker</td>
939
+ </tr>
940
+ <tr>
941
+ <td style="padding:15px">isAlive</td>
942
+ <td style="padding:15px">The array of calls used to get device status for the broker</td>
943
+ </tr>
944
+ <tr>
945
+ <td style="padding:15px">getConfig</td>
946
+ <td style="padding:15px">The array of calls used to get device configuration for the broker</td>
947
+ </tr>
948
+ <tr>
949
+ <td style="padding:15px">getCount</td>
950
+ <td style="padding:15px">The array of calls used to get device configuration for the broker</td>
951
+ </tr>
952
+ <tr>
953
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> path</td>
954
+ <td style="padding:15px">The path, not including the base_path and version, for making this call</td>
955
+ </tr>
956
+ <tr>
957
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> method</td>
958
+ <td style="padding:15px">The rest method for making this call</td>
959
+ </tr>
960
+ <tr>
961
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> query</td>
962
+ <td style="padding:15px">Query object containing and query parameters and their values for this call</td>
963
+ </tr>
964
+ <tr>
965
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> body</td>
966
+ <td style="padding:15px">Body object containing the payload for this call</td>
967
+ </tr>
968
+ <tr>
969
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> headers</td>
970
+ <td style="padding:15px">Header object containing the headers for this call.</td>
971
+ </tr>
972
+ <tr>
973
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> handleFailure</td>
974
+ <td style="padding:15px">Tells the adapter whether to "fail" or "ignore" failures if they occur.</td>
975
+ </tr>
976
+ <tr>
977
+ <td style="padding:15px">isAlive -> statusValue</td>
978
+ <td style="padding:15px">Tells the adapter what value to look for in the status field to determine if the device is alive.</td>
979
+ </tr>
980
+ <tr>
981
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig -> requestFields</td>
982
+ <td style="padding:15px">Object containing fields the adapter should send on the request and where it should get the data. The where can be from a response to a getDevicesFiltered or a static value.</td>
983
+ </tr>
984
+ <tr>
985
+ <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig -> responseFields</td>
986
+ <td style="padding:15px">Object containing fields the adapter should set to send back to iap and where the value should come from in the response or request data.</td>
987
+ </tr>
988
+ </table>
989
+ <br>
990
+
991
+
992
+ ## Using this Adapter
993
+
994
+ The `adapter.js` file contains the calls the adapter makes available to the rest of the Itential Platform. The API detailed for these calls should be available through JSDOC. The following is a brief summary of the calls.
995
+
996
+ ### Generic Adapter Calls
997
+
998
+ These are adapter methods that IAP or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
999
+
1000
+ <table border="1" class="bordered-table">
1001
+ <tr>
1002
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
1003
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
1004
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
1005
+ </tr>
1006
+ <tr>
1007
+ <td style="padding:15px">connect()</td>
1008
+ <td style="padding:15px">This call is run when the Adapter is first loaded by he Itential Platform. It validates the properties have been provided correctly.</td>
1009
+ <td style="padding:15px">No</td>
1010
+ </tr>
1011
+ <tr>
1012
+ <td style="padding:15px">healthCheck(callback)</td>
1013
+ <td style="padding:15px">This call ensures that the adapter can communicate with Adapter for Microsoft Azure DevOps. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
1014
+ <td style="padding:15px">No</td>
1015
+ </tr>
1016
+ <tr>
1017
+ <td style="padding:15px">refreshProperties(properties)</td>
1018
+ <td style="padding:15px">This call provides the adapter the ability to accept property changes without having to restart the adapter.</td>
1019
+ <td style="padding:15px">No</td>
1020
+ </tr>
1021
+ <tr>
1022
+ <td style="padding:15px">encryptProperty(property, technique, callback)</td>
1023
+ <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Adapter for Microsoft Azure DevOps.</td>
1024
+ <td style="padding:15px">No</td>
1025
+ </tr>
1026
+ <tr>
1027
+ <td style="padding:15px">iapUpdateAdapterConfiguration(configFile, changes, entity, type, action, callback)</td>
1028
+ <td style="padding:15px">This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations.</td>
1029
+ <td style="padding:15px">Yes</td>
1030
+ </tr>
1031
+ <tr>
1032
+ <td style="padding:15px">iapSuspendAdapter(mode, callback)</td>
1033
+ <td style="padding:15px">This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed.</td>
1034
+ <td style="padding:15px">Yes</td>
1035
+ </tr>
1036
+ <tr>
1037
+ <td style="padding:15px">iapUnsuspendAdapter(callback)</td>
1038
+ <td style="padding:15px">This call provides the ability to resume a suspended adapter. Any requests in queue will be processed before new requests.</td>
1039
+ <td style="padding:15px">Yes</td>
1040
+ </tr>
1041
+ <tr>
1042
+ <td style="padding:15px">iapGetAdapterQueue(callback)</td>
1043
+ <td style="padding:15px">This call will return the requests that are waiting in the queue if throttling is enabled.</td>
1044
+ <td style="padding:15px">Yes</td>
1045
+ </tr>
1046
+ <tr>
1047
+ <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
1048
+ <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
1049
+ <td style="padding:15px">Yes</td>
1050
+ </tr>
1051
+ <tr>
1052
+ <td style="padding:15px">iapTroubleshootAdapter(props, persistFlag, adapter, callback)</td>
1053
+ <td style="padding:15px">This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls.</td>
1054
+ <td style="padding:15px">Yes</td>
1055
+ </tr>
1056
+ <tr>
1057
+ <td style="padding:15px">iapRunAdapterHealthcheck(adapter, callback)</td>
1058
+ <td style="padding:15px">This call will return the results of a healthcheck.</td>
1059
+ <td style="padding:15px">Yes</td>
1060
+ </tr>
1061
+ <tr>
1062
+ <td style="padding:15px">iapRunAdapterConnectivity(callback)</td>
1063
+ <td style="padding:15px">This call will return the results of a connectivity check.</td>
1064
+ <td style="padding:15px">Yes</td>
1065
+ </tr>
1066
+ <tr>
1067
+ <td style="padding:15px">iapRunAdapterBasicGet(callback)</td>
1068
+ <td style="padding:15px">This call will return the results of running basic get API calls.</td>
1069
+ <td style="padding:15px">Yes</td>
1070
+ </tr>
1071
+ <tr>
1072
+ <td style="padding:15px">iapMoveAdapterEntitiesToDB(callback)</td>
1073
+ <td style="padding:15px">This call will push the adapter configuration from the entities directory into the Adapter or IAP Database.</td>
1074
+ <td style="padding:15px">Yes</td>
1075
+ </tr>
1076
+ <tr>
1077
+ <td style="padding:15px">iapDeactivateTasks(tasks, callback)</td>
1078
+ <td style="padding:15px">This call provides the ability to remove tasks from the adapter.</td>
1079
+ <td style="padding:15px">Yes</td>
1080
+ </tr>
1081
+ <tr>
1082
+ <td style="padding:15px">iapActivateTasks(tasks, callback)</td>
1083
+ <td style="padding:15px">This call provides the ability to add deactivated tasks back into the adapter.</td>
1084
+ <td style="padding:15px">Yes</td>
1085
+ </tr>
1086
+ <tr>
1087
+ <td style="padding:15px">iapExpandedGenericAdapterRequest(metadata, uriPath, restMethod, pathVars, queryData, requestBody, addlHeaders, callback)</td>
1088
+ <td style="padding:15px">This is an expanded Generic Call. The metadata object allows us to provide many new capabilities within the generic request.</td>
1089
+ <td style="padding:15px">Yes</td>
1090
+ </tr>
1091
+ <tr>
1092
+ <td style="padding:15px">genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
1093
+ <td style="padding:15px">This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet.</td>
1094
+ <td style="padding:15px">Yes</td>
1095
+ </tr>
1096
+ <tr>
1097
+ <td style="padding:15px">genericAdapterRequestNoBasePath(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
1098
+ <td style="padding:15px">This call is the same as the genericAdapterRequest only it does not add a base_path or version to the call.</td>
1099
+ <td style="padding:15px">Yes</td>
1100
+ </tr>
1101
+ <tr>
1102
+ <td style="padding:15px">iapRunAdapterLint(callback)</td>
1103
+ <td style="padding:15px">Runs lint on the addapter and provides the information back.</td>
1104
+ <td style="padding:15px">Yes</td>
1105
+ </tr>
1106
+ <tr>
1107
+ <td style="padding:15px">iapRunAdapterTests(callback)</td>
1108
+ <td style="padding:15px">Runs baseunit and unit tests on the adapter and provides the information back.</td>
1109
+ <td style="padding:15px">Yes</td>
1110
+ </tr>
1111
+ <tr>
1112
+ <td style="padding:15px">iapGetAdapterInventory(callback)</td>
1113
+ <td style="padding:15px">This call provides some inventory related information about the adapter.</td>
1114
+ <td style="padding:15px">Yes</td>
1115
+ </tr>
1116
+ </table>
1117
+ <br>
1118
+
1119
+ ### Adapter Cache Calls
1120
+
1121
+ These are adapter methods that are used for adapter caching. If configured, the adapter will cache based on the interval provided. However, you can force a population of the cache manually as well.
1122
+
1123
+ <table border="1" class="bordered-table">
1124
+ <tr>
1125
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
1126
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
1127
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
1128
+ </tr>
1129
+ <tr>
1130
+ <td style="padding:15px">iapPopulateEntityCache(entityTypes, callback)</td>
1131
+ <td style="padding:15px">This call populates the adapter cache.</td>
1132
+ <td style="padding:15px">Yes</td>
1133
+ </tr>
1134
+ <tr>
1135
+ <td style="padding:15px">iapRetrieveEntitiesCache(entityType, options, callback)</td>
1136
+ <td style="padding:15px">This call retrieves the specific items from the adapter cache.</td>
1137
+ <td style="padding:15px">Yes</td>
1138
+ </tr>
1139
+ </table>
1140
+ <br>
1141
+
1142
+ ### Adapter Broker Calls
1143
+
1144
+ These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
1145
+
1146
+ <table border="1" class="bordered-table">
1147
+ <tr>
1148
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
1149
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
1150
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
1151
+ </tr>
1152
+ <tr>
1153
+ <td style="padding:15px">hasEntities(entityType, entityList, callback)</td>
1154
+ <td style="padding:15px">This call is utilized by the IAP Device Broker to determine if the adapter has a specific entity and item of the entity.</td>
1155
+ <td style="padding:15px">No</td>
1156
+ </tr>
1157
+ <tr>
1158
+ <td style="padding:15px">getDevice(deviceName, callback)</td>
1159
+ <td style="padding:15px">This call returns the details of the requested device.</td>
1160
+ <td style="padding:15px">No</td>
1161
+ </tr>
1162
+ <tr>
1163
+ <td style="padding:15px">getDevicesFiltered(options, callback)</td>
1164
+ <td style="padding:15px">This call returns the list of devices that match the criteria provided in the options filter.</td>
1165
+ <td style="padding:15px">No</td>
1166
+ </tr>
1167
+ <tr>
1168
+ <td style="padding:15px">isAlive(deviceName, callback)</td>
1169
+ <td style="padding:15px">This call returns whether the device status is active</td>
1170
+ <td style="padding:15px">No</td>
1171
+ </tr>
1172
+ <tr>
1173
+ <td style="padding:15px">getConfig(deviceName, format, callback)</td>
1174
+ <td style="padding:15px">This call returns the configuration for the selected device.</td>
1175
+ <td style="padding:15px">No</td>
1176
+ </tr>
1177
+ <tr>
1178
+ <td style="padding:15px">iapGetDeviceCount(callback)</td>
1179
+ <td style="padding:15px">This call returns the count of devices.</td>
1180
+ <td style="padding:15px">No</td>
1181
+ </tr>
1182
+ </table>
1183
+ <br>
1184
+
1185
+ ### Specific Adapter Calls
1186
+
1187
+ Specific adapter calls are built based on the API of the Microsoft Azure DevOps. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.
1188
+
1189
+ <table border="1" class="bordered-table">
1190
+ <tr>
1191
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
1192
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
1193
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Path</span></th>
1194
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
1195
+ </tr>
1196
+ <tr>
1197
+ <td style="padding:15px">pipelinesCreate(organization, body, project, apiVersion, callback)</td>
1198
+ <td style="padding:15px">Create a pipeline.</td>
1199
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines?{query}</td>
1200
+ <td style="padding:15px">Yes</td>
1201
+ </tr>
1202
+ <tr>
1203
+ <td style="padding:15px">pipelinesList(organization, project, orderBy, top, continuationToken, apiVersion, callback)</td>
1204
+ <td style="padding:15px">Get a list of pipelines.</td>
1205
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines?{query}</td>
1206
+ <td style="padding:15px">Yes</td>
1207
+ </tr>
1208
+ <tr>
1209
+ <td style="padding:15px">pipelinesGet(organization, project, pipelineId, pipelineVersion, apiVersion, callback)</td>
1210
+ <td style="padding:15px">Gets a pipeline, optionally at the specified version</td>
1211
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}?{query}</td>
1212
+ <td style="padding:15px">Yes</td>
1213
+ </tr>
1214
+ <tr>
1215
+ <td style="padding:15px">previewPreview(organization, body, project, pipelineId, pipelineVersion, apiVersion, callback)</td>
1216
+ <td style="padding:15px">Queues a dry run of the pipeline and returns an object containing the final yaml.</td>
1217
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/preview?{query}</td>
1218
+ <td style="padding:15px">Yes</td>
1219
+ </tr>
1220
+ <tr>
1221
+ <td style="padding:15px">runsList(organization, project, pipelineId, apiVersion, callback)</td>
1222
+ <td style="padding:15px">Gets top 10000 runs for a particular pipeline.</td>
1223
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs?{query}</td>
1224
+ <td style="padding:15px">Yes</td>
1225
+ </tr>
1226
+ <tr>
1227
+ <td style="padding:15px">runsRunPipeline(organization, body, project, pipelineId, pipelineVersion, apiVersion, callback)</td>
1228
+ <td style="padding:15px">Runs a pipeline.</td>
1229
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs?{query}</td>
1230
+ <td style="padding:15px">Yes</td>
1231
+ </tr>
1232
+ <tr>
1233
+ <td style="padding:15px">runsGet(organization, project, pipelineId, runId, apiVersion, callback)</td>
1234
+ <td style="padding:15px">Gets a run for a particular pipeline.</td>
1235
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs/{pathv4}?{query}</td>
1236
+ <td style="padding:15px">Yes</td>
1237
+ </tr>
1238
+ <tr>
1239
+ <td style="padding:15px">artifactsGet(organization, project, pipelineId, runId, artifactName, expand = 'none', apiVersion, callback)</td>
1240
+ <td style="padding:15px">Get a specific artifact from a pipeline run</td>
1241
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs/{pathv4}/artifacts?{query}</td>
1242
+ <td style="padding:15px">Yes</td>
1243
+ </tr>
1244
+ <tr>
1245
+ <td style="padding:15px">logsList(organization, project, pipelineId, runId, expand = 'none', apiVersion, callback)</td>
1246
+ <td style="padding:15px">Get a list of logs from a pipeline run.</td>
1247
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs/{pathv4}/logs?{query}</td>
1248
+ <td style="padding:15px">Yes</td>
1249
+ </tr>
1250
+ <tr>
1251
+ <td style="padding:15px">logsGet(organization, project, pipelineId, runId, logId, expand = 'none', apiVersion, callback)</td>
1252
+ <td style="padding:15px">Get a specific log from a pipeline run</td>
1253
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/pipelines/{pathv3}/runs/{pathv4}/logs/{pathv5}?{query}</td>
1254
+ <td style="padding:15px">Yes</td>
1255
+ </tr>
1256
+ <tr>
1257
+ <td style="padding:15px">repositoriesGetDeletedRepositories(organization, project, apiVersion, callback)</td>
1258
+ <td style="padding:15px">Retrieve deleted git repositories.</td>
1259
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/deletedrepositories?{query}</td>
1260
+ <td style="padding:15px">Yes</td>
1261
+ </tr>
1262
+ <tr>
1263
+ <td style="padding:15px">repositoriesGetRecycleBinRepositories(organization, project, apiVersion, callback)</td>
1264
+ <td style="padding:15px">Retrieve soft-deleted git repositories from the recycle bin.</td>
1265
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/recycleBin/repositories?{query}</td>
1266
+ <td style="padding:15px">Yes</td>
1267
+ </tr>
1268
+ <tr>
1269
+ <td style="padding:15px">repositoriesDeleteRepositoryFromRecycleBin(organization, project, repositoryId, apiVersion, callback)</td>
1270
+ <td style="padding:15px">Destroy (hard delete) a soft-deleted Git repository.</td>
1271
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/recycleBin/repositories/{pathv3}?{query}</td>
1272
+ <td style="padding:15px">Yes</td>
1273
+ </tr>
1274
+ <tr>
1275
+ <td style="padding:15px">repositoriesRestoreRepositoryFromRecycleBin(organization, body, project, repositoryId, apiVersion, callback)</td>
1276
+ <td style="padding:15px">Recover a soft-deleted Git repository. Recently deleted repositories go into a soft-delete state fo</td>
1277
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/recycleBin/repositories/{pathv3}?{query}</td>
1278
+ <td style="padding:15px">Yes</td>
1279
+ </tr>
1280
+ <tr>
1281
+ <td style="padding:15px">repositoriesCreate(organization, body, project, sourceRef, apiVersion, callback)</td>
1282
+ <td style="padding:15px">Create a git repository in a team project.</td>
1283
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories?{query}</td>
1284
+ <td style="padding:15px">Yes</td>
1285
+ </tr>
1286
+ <tr>
1287
+ <td style="padding:15px">repositoriesList(organization, project, includeLinks, includeAllUrls, includeHidden, apiVersion, callback)</td>
1288
+ <td style="padding:15px">Retrieve git repositories.</td>
1289
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories?{query}</td>
1290
+ <td style="padding:15px">Yes</td>
1291
+ </tr>
1292
+ <tr>
1293
+ <td style="padding:15px">repositoriesDelete(organization, repositoryId, project, apiVersion, callback)</td>
1294
+ <td style="padding:15px">Delete a git repository</td>
1295
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}?{query}</td>
1296
+ <td style="padding:15px">Yes</td>
1297
+ </tr>
1298
+ <tr>
1299
+ <td style="padding:15px">repositoriesGetRepository(organization, repositoryId, project, apiVersion, callback)</td>
1300
+ <td style="padding:15px">Retrieve a git repository.</td>
1301
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}?{query}</td>
1302
+ <td style="padding:15px">Yes</td>
1303
+ </tr>
1304
+ <tr>
1305
+ <td style="padding:15px">repositoriesUpdate(organization, body, repositoryId, project, apiVersion, callback)</td>
1306
+ <td style="padding:15px">Updates the Git repository with either a new repo name or a new default branch.</td>
1307
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}?{query}</td>
1308
+ <td style="padding:15px">Yes</td>
1309
+ </tr>
1310
+ <tr>
1311
+ <td style="padding:15px">refsFavoritesCreate(organization, body, project, apiVersion, callback)</td>
1312
+ <td style="padding:15px">Creates a ref favorite</td>
1313
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/favorites/refs?{query}</td>
1314
+ <td style="padding:15px">Yes</td>
1315
+ </tr>
1316
+ <tr>
1317
+ <td style="padding:15px">refsFavoritesList(organization, project, repositoryId, identityId, apiVersion, callback)</td>
1318
+ <td style="padding:15px">Gets the refs favorites for a repo and an identity.</td>
1319
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/favorites/refs?{query}</td>
1320
+ <td style="padding:15px">Yes</td>
1321
+ </tr>
1322
+ <tr>
1323
+ <td style="padding:15px">refsFavoritesDelete(organization, project, favoriteId, apiVersion, callback)</td>
1324
+ <td style="padding:15px">Deletes the refs favorite specified</td>
1325
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/favorites/refs/{pathv3}?{query}</td>
1326
+ <td style="padding:15px">Yes</td>
1327
+ </tr>
1328
+ <tr>
1329
+ <td style="padding:15px">refsFavoritesGet(organization, project, favoriteId, apiVersion, callback)</td>
1330
+ <td style="padding:15px">Gets the refs favorite for a favorite Id.</td>
1331
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/favorites/refs/{pathv3}?{query}</td>
1332
+ <td style="padding:15px">Yes</td>
1333
+ </tr>
1334
+ <tr>
1335
+ <td style="padding:15px">policyConfigurationsGet(organization, project, repositoryId, refName, policyType, top, continuationToken, apiVersion, callback)</td>
1336
+ <td style="padding:15px">Retrieve a list of policy configurations by a given set of scope/filtering criteria.
1337
+
1338
+ Below is a sh</td>
1339
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/policy/configurations?{query}</td>
1340
+ <td style="padding:15px">Yes</td>
1341
+ </tr>
1342
+ <tr>
1343
+ <td style="padding:15px">pullRequestsGetPullRequestsByProject(organization, project, searchCriteriaCreatorId, searchCriteriaIncludeLinks, searchCriteriaRepositoryId, searchCriteriaReviewerId, searchCriteriaSourceRefName, searchCriteriaSourceRepositoryId, searchCriteriaStatus = 'notSet', searchCriteriaTargetRefName, maxCommentLength, skip, top, apiVersion, callback)</td>
1344
+ <td style="padding:15px">Retrieve all pull requests matching a specified criteria.
1345
+
1346
+ Please note that description field will</td>
1347
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/pullrequests?{query}</td>
1348
+ <td style="padding:15px">Yes</td>
1349
+ </tr>
1350
+ <tr>
1351
+ <td style="padding:15px">pullRequestsGetPullRequestById(organization, pullRequestId, project, apiVersion, callback)</td>
1352
+ <td style="padding:15px">Retrieve a pull request.</td>
1353
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/pullrequests/{pathv3}?{query}</td>
1354
+ <td style="padding:15px">Yes</td>
1355
+ </tr>
1356
+ <tr>
1357
+ <td style="padding:15px">pullRequestsCreate(organization, body, repositoryId, project, supportsIterations, apiVersion, callback)</td>
1358
+ <td style="padding:15px">Create a pull request.</td>
1359
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullrequests?{query}</td>
1360
+ <td style="padding:15px">Yes</td>
1361
+ </tr>
1362
+ <tr>
1363
+ <td style="padding:15px">pullRequestsGetPullRequests(organization, repositoryId, project, searchCriteriaCreatorId, searchCriteriaIncludeLinks, searchCriteriaRepositoryId, searchCriteriaReviewerId, searchCriteriaSourceRefName, searchCriteriaSourceRepositoryId, searchCriteriaStatus = 'notSet', searchCriteriaTargetRefName, maxCommentLength, skip, top, apiVersion, callback)</td>
1364
+ <td style="padding:15px">Retrieve all pull requests matching a specified criteria.
1365
+
1366
+ Please note that description field will</td>
1367
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullrequests?{query}</td>
1368
+ <td style="padding:15px">Yes</td>
1369
+ </tr>
1370
+ <tr>
1371
+ <td style="padding:15px">pullRequestsGetPullRequest(organization, repositoryId, pullRequestId, project, maxCommentLength, skip, top, includeCommits, includeWorkItemRefs, apiVersion, callback)</td>
1372
+ <td style="padding:15px">Retrieve a pull request.</td>
1373
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullrequests/{pathv4}?{query}</td>
1374
+ <td style="padding:15px">Yes</td>
1375
+ </tr>
1376
+ <tr>
1377
+ <td style="padding:15px">pullRequestsUpdate(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1378
+ <td style="padding:15px">Update a pull request
1379
+
1380
+ These are the properties that can be updated with the API:
1381
+ - Status
1382
+ - Titl</td>
1383
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullrequests/{pathv4}?{query}</td>
1384
+ <td style="padding:15px">Yes</td>
1385
+ </tr>
1386
+ <tr>
1387
+ <td style="padding:15px">annotatedTagsCreate(organization, body, project, repositoryId, apiVersion, callback)</td>
1388
+ <td style="padding:15px">Create an annotated tag.
1389
+
1390
+ Repositories have both a name and an identifier. Identifiers are globally</td>
1391
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/annotatedtags?{query}</td>
1392
+ <td style="padding:15px">Yes</td>
1393
+ </tr>
1394
+ <tr>
1395
+ <td style="padding:15px">annotatedTagsGet(organization, project, repositoryId, objectId, apiVersion, callback)</td>
1396
+ <td style="padding:15px">Get an annotated tag.
1397
+
1398
+ Repositories have both a name and an identifier. Identifiers are globally un</td>
1399
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/annotatedtags/{pathv4}?{query}</td>
1400
+ <td style="padding:15px">Yes</td>
1401
+ </tr>
1402
+ <tr>
1403
+ <td style="padding:15px">blobsGetBlobsZip(organization, body, repositoryId, project, filename, apiVersion, callback)</td>
1404
+ <td style="padding:15px">Gets one or more blobs in a zip file download.</td>
1405
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/blobs?{query}</td>
1406
+ <td style="padding:15px">Yes</td>
1407
+ </tr>
1408
+ <tr>
1409
+ <td style="padding:15px">blobsGetBlob(organization, repositoryId, sha1, project, download, fileName, format, resolveLfs, apiVersion, callback)</td>
1410
+ <td style="padding:15px">Get a single blob.
1411
+
1412
+ Repositories have both a name and an identifier. Identifiers are globally uniqu</td>
1413
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/blobs/{pathv4}?{query}</td>
1414
+ <td style="padding:15px">Yes</td>
1415
+ </tr>
1416
+ <tr>
1417
+ <td style="padding:15px">cherryPicksCreate(organization, body, project, repositoryId, apiVersion, callback)</td>
1418
+ <td style="padding:15px">Cherry pick a specific commit or commits that are associated to a pull request into a new branch.</td>
1419
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/cherryPicks?{query}</td>
1420
+ <td style="padding:15px">Yes</td>
1421
+ </tr>
1422
+ <tr>
1423
+ <td style="padding:15px">cherryPicksGetCherryPickForRefName(organization, project, repositoryId, refName, apiVersion, callback)</td>
1424
+ <td style="padding:15px">Retrieve information about a cherry pick operation for a specific branch. This operation is expensi</td>
1425
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/cherryPicks?{query}</td>
1426
+ <td style="padding:15px">Yes</td>
1427
+ </tr>
1428
+ <tr>
1429
+ <td style="padding:15px">cherryPicksGetCherryPick(organization, project, cherryPickId, repositoryId, apiVersion, callback)</td>
1430
+ <td style="padding:15px">Retrieve information about a cherry pick operation by cherry pick Id.</td>
1431
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/cherryPicks/{pathv4}?{query}</td>
1432
+ <td style="padding:15px">Yes</td>
1433
+ </tr>
1434
+ <tr>
1435
+ <td style="padding:15px">commitsGetPushCommits(organization, repositoryId, pushId, project, top, skip, includeLinks, apiVersion, callback)</td>
1436
+ <td style="padding:15px">Retrieve a list of commits associated with a particular push.</td>
1437
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits?{query}</td>
1438
+ <td style="padding:15px">Yes</td>
1439
+ </tr>
1440
+ <tr>
1441
+ <td style="padding:15px">commitsGet(organization, commitId, repositoryId, project, changeCount, apiVersion, callback)</td>
1442
+ <td style="padding:15px">Retrieve a particular commit.</td>
1443
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits/{pathv4}?{query}</td>
1444
+ <td style="padding:15px">Yes</td>
1445
+ </tr>
1446
+ <tr>
1447
+ <td style="padding:15px">commitsGetChanges(organization, commitId, repositoryId, project, top, skip, apiVersion, callback)</td>
1448
+ <td style="padding:15px">Retrieve changes for a particular commit.</td>
1449
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits/{pathv4}/changes?{query}</td>
1450
+ <td style="padding:15px">Yes</td>
1451
+ </tr>
1452
+ <tr>
1453
+ <td style="padding:15px">commitsGetCommits(organization, repositoryId, project, skip, top, searchCriteriaAuthor, searchCriteriaCompareVersionVersion, searchCriteriaCompareVersionVersionOptions, searchCriteriaCompareVersionVersionType, searchCriteriaExcludeDeletes, searchCriteriaFromCommitId, searchCriteriaFromDate, searchCriteriaHistoryMode, searchCriteriaIds, searchCriteriaIncludeLinks, searchCriteriaIncludePushData, searchCriteriaIncludeUserImageUrl, searchCriteriaIncludeWorkItems, searchCriteriaItemPath, searchCriteriaItemVersionVersion, searchCriteriaItemVersionVersionOptions, searchCriteriaItemVersionVersionType, searchCriteriaShowOldestCommitsFirst, searchCriteriaToCommitId, searchCriteriaToDate, searchCriteriaUser, apiVersion, callback)</td>
1454
+ <td style="padding:15px">Retrieve git commits for a project.</td>
1455
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits?{query}</td>
1456
+ <td style="padding:15px">Yes</td>
1457
+ </tr>
1458
+ <tr>
1459
+ <td style="padding:15px">commitsGetCommitsBatch(organization, body, repositoryId, project, skip, top, includeStatuses, apiVersion, callback)</td>
1460
+ <td style="padding:15px">Retrieve git commits for a project matching the search criteria</td>
1461
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commitsbatch?{query}</td>
1462
+ <td style="padding:15px">Yes</td>
1463
+ </tr>
1464
+ <tr>
1465
+ <td style="padding:15px">statusesCreate(organization, body, commitId, repositoryId, project, apiVersion, callback)</td>
1466
+ <td style="padding:15px">Create Git commit status.</td>
1467
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits/{pathv4}/statuses?{query}</td>
1468
+ <td style="padding:15px">Yes</td>
1469
+ </tr>
1470
+ <tr>
1471
+ <td style="padding:15px">statusesList(organization, commitId, repositoryId, project, top, skip, latestOnly, apiVersion, callback)</td>
1472
+ <td style="padding:15px">Get statuses associated with the Git commit.</td>
1473
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits/{pathv4}/statuses?{query}</td>
1474
+ <td style="padding:15px">Yes</td>
1475
+ </tr>
1476
+ <tr>
1477
+ <td style="padding:15px">diffsGet(organization, repositoryId, project, diffCommonCommit, top, skip, baseVersion, baseVersionOptions = 'none', baseVersionType = 'branch', targetVersion, targetVersionOptions = 'none', targetVersionType = 'branch', apiVersion, callback)</td>
1478
+ <td style="padding:15px">Find the closest common commit (the merge base) between base and target commits, and get the diff b</td>
1479
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/diffs/commits?{query}</td>
1480
+ <td style="padding:15px">Yes</td>
1481
+ </tr>
1482
+ <tr>
1483
+ <td style="padding:15px">importRequestsCreate(organization, body, project, repositoryId, apiVersion, callback)</td>
1484
+ <td style="padding:15px">Create an import request.</td>
1485
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/importRequests?{query}</td>
1486
+ <td style="padding:15px">Yes</td>
1487
+ </tr>
1488
+ <tr>
1489
+ <td style="padding:15px">importRequestsQuery(organization, project, repositoryId, includeAbandoned, apiVersion, callback)</td>
1490
+ <td style="padding:15px">Retrieve import requests for a repository.</td>
1491
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/importRequests?{query}</td>
1492
+ <td style="padding:15px">Yes</td>
1493
+ </tr>
1494
+ <tr>
1495
+ <td style="padding:15px">importRequestsGet(organization, project, repositoryId, importRequestId, apiVersion, callback)</td>
1496
+ <td style="padding:15px">Retrieve a particular import request.</td>
1497
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/importRequests/{pathv4}?{query}</td>
1498
+ <td style="padding:15px">Yes</td>
1499
+ </tr>
1500
+ <tr>
1501
+ <td style="padding:15px">importRequestsUpdate(organization, body, project, repositoryId, importRequestId, apiVersion, callback)</td>
1502
+ <td style="padding:15px">Retry or abandon a failed import request.
1503
+
1504
+ There can only be one active import request associated w</td>
1505
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/importRequests/{pathv4}?{query}</td>
1506
+ <td style="padding:15px">Yes</td>
1507
+ </tr>
1508
+ <tr>
1509
+ <td style="padding:15px">itemsList(organization, repositoryId, project, itemPath, scopePath, recursionLevel = 'none', includeContentMetadata, latestProcessedChange, download, includeLinks, includeContent, resolveLfs, format, versionDescriptorVersion, versionDescriptorVersionOptions = 'none', versionDescriptorVersionType = 'branch', apiVersion, callback)</td>
1510
+ <td style="padding:15px">Get Item Metadata and/or Content for a collection of items. The download parameter is to indicate w</td>
1511
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/items?{query}</td>
1512
+ <td style="padding:15px">Yes</td>
1513
+ </tr>
1514
+ <tr>
1515
+ <td style="padding:15px">itemsGetItemsBatch(organization, body, repositoryId, project, apiVersion, callback)</td>
1516
+ <td style="padding:15px">Post for retrieving a creating a batch out of a set of items in a repo / project given a list of pa</td>
1517
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/itemsbatch?{query}</td>
1518
+ <td style="padding:15px">Yes</td>
1519
+ </tr>
1520
+ <tr>
1521
+ <td style="padding:15px">pullRequestQueryGet(organization, body, repositoryId, project, apiVersion, callback)</td>
1522
+ <td style="padding:15px">This API is used to find what pull requests are related to a given commit. It can be used to eithe</td>
1523
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullrequestquery?{query}</td>
1524
+ <td style="padding:15px">Yes</td>
1525
+ </tr>
1526
+ <tr>
1527
+ <td style="padding:15px">pullRequestAttachmentsList(organization, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1528
+ <td style="padding:15px">Get a list of files attached to a given pull request.</td>
1529
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/attachments?{query}</td>
1530
+ <td style="padding:15px">Yes</td>
1531
+ </tr>
1532
+ <tr>
1533
+ <td style="padding:15px">pullRequestAttachmentsCreate(organization, body, fileName, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1534
+ <td style="padding:15px">Attach a new file to a pull request.</td>
1535
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/attachments/{pathv5}?{query}</td>
1536
+ <td style="padding:15px">Yes</td>
1537
+ </tr>
1538
+ <tr>
1539
+ <td style="padding:15px">pullRequestAttachmentsDelete(organization, fileName, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1540
+ <td style="padding:15px">Delete a pull request attachment.</td>
1541
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/attachments/{pathv5}?{query}</td>
1542
+ <td style="padding:15px">Yes</td>
1543
+ </tr>
1544
+ <tr>
1545
+ <td style="padding:15px">pullRequestAttachmentsGet(organization, fileName, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1546
+ <td style="padding:15px">Get the file content of a pull request attachment.</td>
1547
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/attachments/{pathv5}?{query}</td>
1548
+ <td style="padding:15px">Yes</td>
1549
+ </tr>
1550
+ <tr>
1551
+ <td style="padding:15px">pullRequestCommitsGetPullRequestCommits(organization, repositoryId, pullRequestId, project, top, continuationToken, apiVersion, callback)</td>
1552
+ <td style="padding:15px">Get the commits for the specified pull request.</td>
1553
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/commits?{query}</td>
1554
+ <td style="padding:15px">Yes</td>
1555
+ </tr>
1556
+ <tr>
1557
+ <td style="padding:15px">pullRequestCommitsGetPullRequestIterationCommits(organization, repositoryId, pullRequestId, iterationId, project, top, skip, apiVersion, callback)</td>
1558
+ <td style="padding:15px">Get the commits for the specified iteration of a pull request.</td>
1559
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/commits?{query}</td>
1560
+ <td style="padding:15px">Yes</td>
1561
+ </tr>
1562
+ <tr>
1563
+ <td style="padding:15px">pullRequestIterationsList(organization, repositoryId, pullRequestId, project, includeCommits, apiVersion, callback)</td>
1564
+ <td style="padding:15px">Get the list of iterations for the specified pull request.</td>
1565
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations?{query}</td>
1566
+ <td style="padding:15px">Yes</td>
1567
+ </tr>
1568
+ <tr>
1569
+ <td style="padding:15px">pullRequestIterationsGet(organization, repositoryId, pullRequestId, iterationId, project, apiVersion, callback)</td>
1570
+ <td style="padding:15px">Get the specified iteration for a pull request.</td>
1571
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}?{query}</td>
1572
+ <td style="padding:15px">Yes</td>
1573
+ </tr>
1574
+ <tr>
1575
+ <td style="padding:15px">pullRequestIterationChangesGet(organization, repositoryId, pullRequestId, iterationId, project, top, skip, compareTo, apiVersion, callback)</td>
1576
+ <td style="padding:15px">Retrieve the changes made in a pull request between two iterations.</td>
1577
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/changes?{query}</td>
1578
+ <td style="padding:15px">Yes</td>
1579
+ </tr>
1580
+ <tr>
1581
+ <td style="padding:15px">pullRequestIterationStatusesCreate(organization, body, repositoryId, pullRequestId, iterationId, project, apiVersion, callback)</td>
1582
+ <td style="padding:15px">Create a pull request status on the iteration. This operation will have the same result as Create s</td>
1583
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/statuses?{query}</td>
1584
+ <td style="padding:15px">Yes</td>
1585
+ </tr>
1586
+ <tr>
1587
+ <td style="padding:15px">pullRequestIterationStatusesList(organization, repositoryId, pullRequestId, iterationId, project, apiVersion, callback)</td>
1588
+ <td style="padding:15px">Get all the statuses associated with a pull request iteration.</td>
1589
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/statuses?{query}</td>
1590
+ <td style="padding:15px">Yes</td>
1591
+ </tr>
1592
+ <tr>
1593
+ <td style="padding:15px">pullRequestIterationStatusesUpdate(organization, body, repositoryId, pullRequestId, iterationId, project, apiVersion, callback)</td>
1594
+ <td style="padding:15px">Update pull request iteration statuses collection. The only supported operation type is `remove`.
1595
+
1596
+ </td>
1597
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/statuses?{query}</td>
1598
+ <td style="padding:15px">Yes</td>
1599
+ </tr>
1600
+ <tr>
1601
+ <td style="padding:15px">pullRequestIterationStatusesDelete(organization, repositoryId, pullRequestId, iterationId, statusId, project, apiVersion, callback)</td>
1602
+ <td style="padding:15px">Delete pull request iteration status.
1603
+
1604
+ You can remove multiple statuses in one call by using Update</td>
1605
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/statuses/{pathv6}?{query}</td>
1606
+ <td style="padding:15px">Yes</td>
1607
+ </tr>
1608
+ <tr>
1609
+ <td style="padding:15px">pullRequestIterationStatusesGet(organization, repositoryId, pullRequestId, iterationId, statusId, project, apiVersion, callback)</td>
1610
+ <td style="padding:15px">Get the specific pull request iteration status by ID. The status ID is unique within the pull reque</td>
1611
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/iterations/{pathv5}/statuses/{pathv6}?{query}</td>
1612
+ <td style="padding:15px">Yes</td>
1613
+ </tr>
1614
+ <tr>
1615
+ <td style="padding:15px">pullRequestLabelsCreate(organization, body, repositoryId, pullRequestId, project, projectId, apiVersion, callback)</td>
1616
+ <td style="padding:15px">Create a label for a specified pull request. The only required field is the name of the new label.</td>
1617
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/labels?{query}</td>
1618
+ <td style="padding:15px">Yes</td>
1619
+ </tr>
1620
+ <tr>
1621
+ <td style="padding:15px">pullRequestLabelsList(organization, repositoryId, pullRequestId, project, projectId, apiVersion, callback)</td>
1622
+ <td style="padding:15px">Get all the labels assigned to a pull request.</td>
1623
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/labels?{query}</td>
1624
+ <td style="padding:15px">Yes</td>
1625
+ </tr>
1626
+ <tr>
1627
+ <td style="padding:15px">pullRequestLabelsDelete(organization, repositoryId, pullRequestId, labelIdOrName, project, projectId, apiVersion, callback)</td>
1628
+ <td style="padding:15px">Removes a label from the set of those assigned to the pull request.</td>
1629
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/labels/{pathv5}?{query}</td>
1630
+ <td style="padding:15px">Yes</td>
1631
+ </tr>
1632
+ <tr>
1633
+ <td style="padding:15px">pullRequestLabelsGet(organization, repositoryId, pullRequestId, labelIdOrName, project, projectId, apiVersion, callback)</td>
1634
+ <td style="padding:15px">Retrieves a single label that has been assigned to a pull request.</td>
1635
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/labels/{pathv5}?{query}</td>
1636
+ <td style="padding:15px">Yes</td>
1637
+ </tr>
1638
+ <tr>
1639
+ <td style="padding:15px">pullRequestPropertiesList(organization, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1640
+ <td style="padding:15px">Get external properties of the pull request.</td>
1641
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/properties?{query}</td>
1642
+ <td style="padding:15px">Yes</td>
1643
+ </tr>
1644
+ <tr>
1645
+ <td style="padding:15px">pullRequestPropertiesUpdate(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1646
+ <td style="padding:15px">Create or update pull request external properties. The patch operation can be `add`, `replace` or `</td>
1647
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/properties?{query}</td>
1648
+ <td style="padding:15px">Yes</td>
1649
+ </tr>
1650
+ <tr>
1651
+ <td style="padding:15px">pullRequestReviewersCreatePullRequestReviewers(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1652
+ <td style="padding:15px">Add reviewers to a pull request.</td>
1653
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers?{query}</td>
1654
+ <td style="padding:15px">Yes</td>
1655
+ </tr>
1656
+ <tr>
1657
+ <td style="padding:15px">pullRequestReviewersCreateUnmaterializedPullRequestReviewer(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1658
+ <td style="padding:15px">Add an unmaterialized identity to the reviewers of a pull request.</td>
1659
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers?{query}</td>
1660
+ <td style="padding:15px">Yes</td>
1661
+ </tr>
1662
+ <tr>
1663
+ <td style="padding:15px">pullRequestReviewersList(organization, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1664
+ <td style="padding:15px">Retrieve the reviewers for a pull request</td>
1665
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers?{query}</td>
1666
+ <td style="padding:15px">Yes</td>
1667
+ </tr>
1668
+ <tr>
1669
+ <td style="padding:15px">pullRequestReviewersUpdatePullRequestReviewers(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1670
+ <td style="padding:15px">Reset the votes of multiple reviewers on a pull request. NOTE: This endpoint only supports updatin</td>
1671
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers?{query}</td>
1672
+ <td style="padding:15px">Yes</td>
1673
+ </tr>
1674
+ <tr>
1675
+ <td style="padding:15px">pullRequestReviewersCreatePullRequestReviewer(organization, body, repositoryId, pullRequestId, reviewerId, project, apiVersion, callback)</td>
1676
+ <td style="padding:15px">Add a reviewer to a pull request or cast a vote.</td>
1677
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers/{pathv5}?{query}</td>
1678
+ <td style="padding:15px">Yes</td>
1679
+ </tr>
1680
+ <tr>
1681
+ <td style="padding:15px">pullRequestReviewersDelete(organization, repositoryId, pullRequestId, reviewerId, project, apiVersion, callback)</td>
1682
+ <td style="padding:15px">Remove a reviewer from a pull request.</td>
1683
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers/{pathv5}?{query}</td>
1684
+ <td style="padding:15px">Yes</td>
1685
+ </tr>
1686
+ <tr>
1687
+ <td style="padding:15px">pullRequestReviewersGet(organization, repositoryId, pullRequestId, reviewerId, project, apiVersion, callback)</td>
1688
+ <td style="padding:15px">Retrieve information about a particular reviewer on a pull request</td>
1689
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers/{pathv5}?{query}</td>
1690
+ <td style="padding:15px">Yes</td>
1691
+ </tr>
1692
+ <tr>
1693
+ <td style="padding:15px">pullRequestReviewersUpdatePullRequestReviewer(organization, body, repositoryId, pullRequestId, reviewerId, project, apiVersion, callback)</td>
1694
+ <td style="padding:15px">Edit a reviewer entry. These fields are patchable: isFlagged, hasDeclined</td>
1695
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/reviewers/{pathv5}?{query}</td>
1696
+ <td style="padding:15px">Yes</td>
1697
+ </tr>
1698
+ <tr>
1699
+ <td style="padding:15px">pullRequestShareSharePullRequest(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1700
+ <td style="padding:15px">Sends an e-mail notification about a specific pull request to a set of recipients</td>
1701
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/share?{query}</td>
1702
+ <td style="padding:15px">Yes</td>
1703
+ </tr>
1704
+ <tr>
1705
+ <td style="padding:15px">pullRequestStatusesCreate(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1706
+ <td style="padding:15px">Create a pull request status.
1707
+
1708
+ The only required field for the status is `Context.Name` that unique</td>
1709
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/statuses?{query}</td>
1710
+ <td style="padding:15px">Yes</td>
1711
+ </tr>
1712
+ <tr>
1713
+ <td style="padding:15px">pullRequestStatusesList(organization, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1714
+ <td style="padding:15px">Get all the statuses associated with a pull request.</td>
1715
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/statuses?{query}</td>
1716
+ <td style="padding:15px">Yes</td>
1717
+ </tr>
1718
+ <tr>
1719
+ <td style="padding:15px">pullRequestStatusesUpdate(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1720
+ <td style="padding:15px">Update pull request statuses collection. The only supported operation type is `remove`.
1721
+
1722
+ This opera</td>
1723
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/statuses?{query}</td>
1724
+ <td style="padding:15px">Yes</td>
1725
+ </tr>
1726
+ <tr>
1727
+ <td style="padding:15px">pullRequestStatusesDelete(organization, repositoryId, pullRequestId, statusId, project, apiVersion, callback)</td>
1728
+ <td style="padding:15px">Delete pull request status.
1729
+
1730
+ You can remove multiple statuses in one call by using Update operation.</td>
1731
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/statuses/{pathv5}?{query}</td>
1732
+ <td style="padding:15px">Yes</td>
1733
+ </tr>
1734
+ <tr>
1735
+ <td style="padding:15px">pullRequestStatusesGet(organization, repositoryId, pullRequestId, statusId, project, apiVersion, callback)</td>
1736
+ <td style="padding:15px">Get the specific pull request status by ID. The status ID is unique within the pull request across</td>
1737
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/statuses/{pathv5}?{query}</td>
1738
+ <td style="padding:15px">Yes</td>
1739
+ </tr>
1740
+ <tr>
1741
+ <td style="padding:15px">pullRequestThreadsCreate(organization, body, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1742
+ <td style="padding:15px">Create a thread in a pull request.</td>
1743
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads?{query}</td>
1744
+ <td style="padding:15px">Yes</td>
1745
+ </tr>
1746
+ <tr>
1747
+ <td style="padding:15px">pullRequestThreadsList(organization, repositoryId, pullRequestId, project, iteration, baseIteration, apiVersion, callback)</td>
1748
+ <td style="padding:15px">Retrieve all threads in a pull request.</td>
1749
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads?{query}</td>
1750
+ <td style="padding:15px">Yes</td>
1751
+ </tr>
1752
+ <tr>
1753
+ <td style="padding:15px">pullRequestThreadsGet(organization, repositoryId, pullRequestId, threadId, project, iteration, baseIteration, apiVersion, callback)</td>
1754
+ <td style="padding:15px">Retrieve a thread in a pull request.</td>
1755
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}?{query}</td>
1756
+ <td style="padding:15px">Yes</td>
1757
+ </tr>
1758
+ <tr>
1759
+ <td style="padding:15px">pullRequestThreadsUpdate(organization, body, repositoryId, pullRequestId, threadId, project, apiVersion, callback)</td>
1760
+ <td style="padding:15px">Update a thread in a pull request.</td>
1761
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}?{query}</td>
1762
+ <td style="padding:15px">Yes</td>
1763
+ </tr>
1764
+ <tr>
1765
+ <td style="padding:15px">pullRequestThreadCommentsCreate(organization, body, repositoryId, pullRequestId, threadId, project, apiVersion, callback)</td>
1766
+ <td style="padding:15px">Create a comment on a specific thread in a pull request (up to 500 comments can be created per thre</td>
1767
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments?{query}</td>
1768
+ <td style="padding:15px">Yes</td>
1769
+ </tr>
1770
+ <tr>
1771
+ <td style="padding:15px">pullRequestThreadCommentsList(organization, repositoryId, pullRequestId, threadId, project, apiVersion, callback)</td>
1772
+ <td style="padding:15px">Retrieve all comments associated with a specific thread in a pull request.</td>
1773
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments?{query}</td>
1774
+ <td style="padding:15px">Yes</td>
1775
+ </tr>
1776
+ <tr>
1777
+ <td style="padding:15px">pullRequestThreadCommentsDelete(organization, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1778
+ <td style="padding:15px">Delete a comment associated with a specific thread in a pull request.</td>
1779
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}?{query}</td>
1780
+ <td style="padding:15px">Yes</td>
1781
+ </tr>
1782
+ <tr>
1783
+ <td style="padding:15px">pullRequestThreadCommentsGet(organization, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1784
+ <td style="padding:15px">Retrieve a comment associated with a specific thread in a pull request.</td>
1785
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}?{query}</td>
1786
+ <td style="padding:15px">Yes</td>
1787
+ </tr>
1788
+ <tr>
1789
+ <td style="padding:15px">pullRequestThreadCommentsUpdate(organization, body, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1790
+ <td style="padding:15px">Update a comment associated with a specific thread in a pull request.</td>
1791
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}?{query}</td>
1792
+ <td style="padding:15px">Yes</td>
1793
+ </tr>
1794
+ <tr>
1795
+ <td style="padding:15px">pullRequestCommentLikesCreate(organization, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1796
+ <td style="padding:15px">Add a like on a comment.</td>
1797
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}/likes?{query}</td>
1798
+ <td style="padding:15px">Yes</td>
1799
+ </tr>
1800
+ <tr>
1801
+ <td style="padding:15px">pullRequestCommentLikesDelete(organization, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1802
+ <td style="padding:15px">Delete a like on a comment.</td>
1803
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}/likes?{query}</td>
1804
+ <td style="padding:15px">Yes</td>
1805
+ </tr>
1806
+ <tr>
1807
+ <td style="padding:15px">pullRequestCommentLikesList(organization, repositoryId, pullRequestId, threadId, commentId, project, apiVersion, callback)</td>
1808
+ <td style="padding:15px">Get likes for a comment.</td>
1809
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/threads/{pathv5}/comments/{pathv6}/likes?{query}</td>
1810
+ <td style="padding:15px">Yes</td>
1811
+ </tr>
1812
+ <tr>
1813
+ <td style="padding:15px">pullRequestWorkItemsList(organization, repositoryId, pullRequestId, project, apiVersion, callback)</td>
1814
+ <td style="padding:15px">Retrieve a list of work items associated with a pull request.</td>
1815
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pullRequests/{pathv4}/workitems?{query}</td>
1816
+ <td style="padding:15px">Yes</td>
1817
+ </tr>
1818
+ <tr>
1819
+ <td style="padding:15px">pushesCreate(organization, body, repositoryId, project, apiVersion, callback)</td>
1820
+ <td style="padding:15px">Push changes to the repository.</td>
1821
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pushes?{query}</td>
1822
+ <td style="padding:15px">Yes</td>
1823
+ </tr>
1824
+ <tr>
1825
+ <td style="padding:15px">pushesList(organization, repositoryId, project, skip, top, searchCriteriaFromDate, searchCriteriaIncludeLinks, searchCriteriaIncludeRefUpdates, searchCriteriaPusherId, searchCriteriaRefName, searchCriteriaToDate, apiVersion, callback)</td>
1826
+ <td style="padding:15px">Retrieves pushes associated with the specified repository.</td>
1827
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pushes?{query}</td>
1828
+ <td style="padding:15px">Yes</td>
1829
+ </tr>
1830
+ <tr>
1831
+ <td style="padding:15px">pushesGet(organization, repositoryId, pushId, project, includeCommits, includeRefUpdates, apiVersion, callback)</td>
1832
+ <td style="padding:15px">Retrieves a particular push.</td>
1833
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/pushes/{pathv4}?{query}</td>
1834
+ <td style="padding:15px">Yes</td>
1835
+ </tr>
1836
+ <tr>
1837
+ <td style="padding:15px">refsList(organization, repositoryId, project, filter, includeLinks, includeStatuses, includeMyBranches, latestStatusesOnly, peelTags, filterContains, top, continuationToken, apiVersion, callback)</td>
1838
+ <td style="padding:15px">Queries the provided repository for its refs and returns them.</td>
1839
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/refs?{query}</td>
1840
+ <td style="padding:15px">Yes</td>
1841
+ </tr>
1842
+ <tr>
1843
+ <td style="padding:15px">refsUpdateRef(organization, body, repositoryId, filter, project, projectId, apiVersion, callback)</td>
1844
+ <td style="padding:15px">Lock or Unlock a branch.</td>
1845
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/refs?{query}</td>
1846
+ <td style="padding:15px">Yes</td>
1847
+ </tr>
1848
+ <tr>
1849
+ <td style="padding:15px">refsUpdateRefs(organization, body, repositoryId, project, projectId, apiVersion, callback)</td>
1850
+ <td style="padding:15px">Creating, updating, or deleting refs(branches).
1851
+
1852
+ Updating a ref means making it point at a differen</td>
1853
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/refs?{query}</td>
1854
+ <td style="padding:15px">Yes</td>
1855
+ </tr>
1856
+ <tr>
1857
+ <td style="padding:15px">revertsCreate(organization, body, project, repositoryId, apiVersion, callback)</td>
1858
+ <td style="padding:15px">Starts the operation to create a new branch which reverts changes introduced by either a specific c</td>
1859
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/reverts?{query}</td>
1860
+ <td style="padding:15px">Yes</td>
1861
+ </tr>
1862
+ <tr>
1863
+ <td style="padding:15px">revertsGetRevertForRefName(organization, project, repositoryId, refName, apiVersion, callback)</td>
1864
+ <td style="padding:15px">Retrieve information about a revert operation for a specific branch.</td>
1865
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/reverts?{query}</td>
1866
+ <td style="padding:15px">Yes</td>
1867
+ </tr>
1868
+ <tr>
1869
+ <td style="padding:15px">revertsGetRevert(organization, project, revertId, repositoryId, apiVersion, callback)</td>
1870
+ <td style="padding:15px">Retrieve information about a revert operation by revert Id.</td>
1871
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/reverts/{pathv4}?{query}</td>
1872
+ <td style="padding:15px">Yes</td>
1873
+ </tr>
1874
+ <tr>
1875
+ <td style="padding:15px">statsList(organization, repositoryId, project, baseVersionDescriptorVersion, baseVersionDescriptorVersionOptions = 'none', baseVersionDescriptorVersionType = 'branch', apiVersion, callback)</td>
1876
+ <td style="padding:15px">Retrieve statistics about all branches within a repository.</td>
1877
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/stats/branches?{query}</td>
1878
+ <td style="padding:15px">Yes</td>
1879
+ </tr>
1880
+ <tr>
1881
+ <td style="padding:15px">suggestionsList(organization, repositoryId, project, apiVersion, callback)</td>
1882
+ <td style="padding:15px">Retrieve a pull request suggestion for a particular repository or team project.</td>
1883
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/suggestions?{query}</td>
1884
+ <td style="padding:15px">Yes</td>
1885
+ </tr>
1886
+ <tr>
1887
+ <td style="padding:15px">treesGet(organization, repositoryId, sha1, project, projectId, recursive, fileName, format, apiVersion, callback)</td>
1888
+ <td style="padding:15px">The Tree endpoint returns the collection of objects underneath the specified tree. Trees are folder</td>
1889
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/trees/{pathv4}?{query}</td>
1890
+ <td style="padding:15px">Yes</td>
1891
+ </tr>
1892
+ <tr>
1893
+ <td style="padding:15px">mergeBasesList(organization, repositoryNameOrId, commitId, otherCommitId, project, otherCollectionId, otherRepositoryId, apiVersion, callback)</td>
1894
+ <td style="padding:15px">Find the merge bases of two commits, optionally across forks. If otherRepositoryId is not specified</td>
1895
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/commits/{pathv4}/mergebases?{query}</td>
1896
+ <td style="padding:15px">Yes</td>
1897
+ </tr>
1898
+ <tr>
1899
+ <td style="padding:15px">forksList(organization, repositoryNameOrId, collectionId, project, includeLinks, apiVersion, callback)</td>
1900
+ <td style="padding:15px">Retrieve all forks of a repository in the collection.</td>
1901
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/forks/{pathv4}?{query}</td>
1902
+ <td style="padding:15px">Yes</td>
1903
+ </tr>
1904
+ <tr>
1905
+ <td style="padding:15px">forksCreateForkSyncRequest(organization, body, repositoryNameOrId, project, includeLinks, apiVersion, callback)</td>
1906
+ <td style="padding:15px">Request that another repository's refs be fetched into this one. It syncs two existing forks. To cr</td>
1907
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/forkSyncRequests?{query}</td>
1908
+ <td style="padding:15px">Yes</td>
1909
+ </tr>
1910
+ <tr>
1911
+ <td style="padding:15px">forksGetForkSyncRequests(organization, repositoryNameOrId, project, includeAbandoned, includeLinks, apiVersion, callback)</td>
1912
+ <td style="padding:15px">Retrieve all requested fork sync operations on this repository.</td>
1913
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/forkSyncRequests?{query}</td>
1914
+ <td style="padding:15px">Yes</td>
1915
+ </tr>
1916
+ <tr>
1917
+ <td style="padding:15px">forksGetForkSyncRequest(organization, repositoryNameOrId, forkSyncOperationId, project, includeLinks, apiVersion, callback)</td>
1918
+ <td style="padding:15px">Get a specific fork sync operation's details.</td>
1919
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/forkSyncRequests/{pathv4}?{query}</td>
1920
+ <td style="padding:15px">Yes</td>
1921
+ </tr>
1922
+ <tr>
1923
+ <td style="padding:15px">mergesCreate(organization, body, project, repositoryNameOrId, includeLinks, apiVersion, callback)</td>
1924
+ <td style="padding:15px">Request a git merge operation. Currently we support merging only 2 commits.</td>
1925
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/merges?{query}</td>
1926
+ <td style="padding:15px">Yes</td>
1927
+ </tr>
1928
+ <tr>
1929
+ <td style="padding:15px">mergesGet(organization, project, repositoryNameOrId, mergeOperationId, includeLinks, apiVersion, callback)</td>
1930
+ <td style="padding:15px">Get a specific merge operation's details.</td>
1931
+ <td style="padding:15px">{base_path}/{version}/{pathv1}/{pathv2}/_apis/git/repositories/{pathv3}/merges/{pathv4}?{query}</td>
1932
+ <td style="padding:15px">Yes</td>
1933
+ </tr>
1934
+ </table>
1935
+ <br>
1936
+
1937
+ ### Authentication
1938
+
1939
+ This document will go through the steps for authenticating the Microsoft Azure DevOps adapter with the authentication methods we have worked with in the past. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://docs.itential.com/opensource/docs/authentication" target="_blank">HERE</a>.
1940
+
1941
+ #### Static Token Authentication
1942
+ The Microsoft Azure DevOps adapter requires Static Token Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
1943
+
1944
+ STEPS
1945
+ 1. Ensure you have access to a Microsoft Azure DevOps server and that it is running
1946
+ 2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
1947
+ 3. Use the properties below for the ```properties.authentication``` field
1948
+ ```json
1949
+ "authentication": {
1950
+ "auth_method": "static_token",
1951
+ "token": "<PAT>",
1952
+ "token_timeout": 600000,
1953
+ "token_cache": "local",
1954
+ "invalid_token_error": 401,
1955
+ "auth_field": "header.headers.Authorization",
1956
+ "auth_field_format": "Basic {b64}Basic:{token}{/b64}",
1957
+ "auth_logging": false
1958
+ }
1959
+ ```
1960
+ you can leave all of the other properties in the authentication section, they will not be used when the auth_method is static_token.
1961
+
1962
+ 4. Restart the adapter. If your properties were set correctly, the adapter should go online.
1963
+
1964
+ #### Troubleshooting
1965
+ - Make sure you copied over the correct username and password.
1966
+ - Turn on debug level logs for the adapter in IAP Admin Essentials.
1967
+ - Turn on auth_logging for the adapter in IAP Admin Essentials (adapter properties).
1968
+ - Investigate the logs - in particular:
1969
+ - The FULL REQUEST log to make sure the proper headers are being sent with the request.
1970
+ - The FULL BODY log to make sure the payload is accurate.
1971
+ - The CALL RETURN log to see what the other system is telling us.
1972
+ - Credentials should be ** masked ** by the adapter so make sure you verify the username and password - including that there are erroneous spaces at the front or end.
1973
+ - Remember when you are done to turn auth_logging off as you do not want to log credentials.
1974
+
1975
+ ## Additional Information
1976
+
1977
+ ### Enhancements
1978
+
1979
+ #### Adding a Second Instance of an Adapter
1980
+
1981
+ You can add a second instance of this adapter without adding new code on the file system. To do this go into the IAP Admin Essentials and add a new service config for this adapter. The two instances of the adapter should have unique ids. In addition, they should point to different instances (unique host and port) of the other system.
1982
+
1983
+ #### Adding Adapter Calls
1984
+
1985
+ There are multiple ways to add calls to an existing adapter.
1986
+
1987
+ The easiest way would be to use the Adapter Builder update process. This process takes in a Swagger or OpenAPI document, allows you to select the calls you want to add and then generates a zip file that can be used to update the adapter. Once you have the zip file simply put it in the adapter directory and execute `npm run adapter:update`.
1988
+
1989
+ ```bash
1990
+ mv updatePackage.zip adapter-azure_devops
1991
+ cd adapter-azure_devops
1992
+ npm run adapter:update
1993
+ ```
1994
+
1995
+ If you do not have a Swagger or OpenAPI document, you can use a Postman Collection and convert that to an OpenAPI document using APIMatic and then follow the first process.
1996
+
1997
+ If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
1998
+
1999
+ ```text
2000
+ Files to update
2001
+ * entities/<entity>/action.json: add an action
2002
+ * entities/<entity>/schema.json (or the schema defined on the action): add action to the enum for ph_request_type
2003
+ * adapter.js: add the new method and make sure it calls the proper entity and action
2004
+ * pronghorn.json: add the new method
2005
+ * test/unit/adapterTestUnit.js (optional but best practice): add unit test(s) - function is there, any required parameters error when not passed in
2006
+ * test/integration/adapterTestIntegration.js (optional but best practice): add integration test
2007
+ ```
2008
+
2009
+ #### Adding Adapter Properties
2010
+
2011
+ While changing adapter properties is done in the service instance configuration section of IAP, adding properties has to be done in the adapter. To add a property you should edit the propertiesSchema.json with the proper information for the property. In addition, you should modify the sampleProperties to have the new property in it.
2012
+
2013
+ ```text
2014
+ Files to update
2015
+ * propertiesSchema.json: add the new property and how it is defined
2016
+ * sampleProperties: add the new property with a default value
2017
+ * test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
2018
+ * test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
2019
+ ```
2020
+
2021
+ #### Changing Adapter Authentication
2022
+
2023
+ Often an adapter is built before knowing the authentication and authentication processes can also change over time. The adapter supports many different kinds of authentication but it does require configuration. Some forms of authentication can be defined entirely with the adapter properties but others require configuration.
2024
+
2025
+ ```text
2026
+ Files to update
2027
+ * entities/.system/action.json: change the getToken action as needed
2028
+ * entities/.system/schemaTokenReq.json: add input parameters (external name is name in other system)
2029
+ * entities/.system/schemaTokenResp.json: add response parameters (external name is name in other system)
2030
+ * propertiesSchema.json: add any new property and how it is defined
2031
+ * sampleProperties: add any new property with a default value
2032
+ * test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
2033
+ * test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
2034
+ ```
2035
+
2036
+ #### Enhancing Adapter Integration Tests
2037
+
2038
+ The adapter integration tests are written to be able to test in either stub (standalone) mode or integrated to the other system. However, if integrating to the other system, you may need to provide better data than what the adapter provides by default as that data is likely to fail for create and update. To provide better data, edit the adapter integration test file. Make sure you do not remove the marker and keep custom code below the marker so you do not impact future migrations. Once the edits are complete, run the integration test as it instructs you to above. When you run integrated to the other system, you can also save mockdata for future use by changing the isSaveMockData flag to true.
2039
+
2040
+ ```text
2041
+ Files to update
2042
+ * test/integration/adapterTestIntegration.js: add better data for the create and update calls so that they will not fail.
2043
+ ```
2044
+
2045
+ As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
2046
+
2047
+ ### Contributing
2048
+
2049
+ First off, thanks for taking the time to contribute!
2050
+
2051
+ The following is a set of rules for contributing.
2052
+
2053
+ #### Code of Conduct
2054
+
2055
+ This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to support@itential.com.
2056
+
2057
+ #### How to Contribute
2058
+
2059
+ Follow the contributing guide (here)[https://gitlab.com/itentialopensource/adapters/contributing-guide]
2060
+
2061
+ ### Helpful Links
2062
+
2063
+ <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
2064
+
2065
+ ### Node Scripts
2066
+
2067
+ There are several node scripts that now accompany the adapter. These scripts are provided to make several activities easier. Many of these scripts can have issues with different versions of IAP as they have dependencies on IAP and Mongo. If you have issues with the scripts please report them to the Itential Adapter Team. Each of these scripts are described below.
2068
+
2069
+ <table border="1" class="bordered-table">
2070
+ <tr>
2071
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Run</span></th>
2072
+ <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
2073
+ </tr>
2074
+ <tr>
2075
+ <td style="padding:15px">npm run adapter:install</td>
2076
+ <td style="padding:15px">Provides an easier way to install the adapter.</td>
2077
+ </tr>
2078
+ <tr>
2079
+ <td style="padding:15px">npm run adapter:checkMigrate</td>
2080
+ <td style="padding:15px">Checks whether your adapter can and should be migrated to the latest foundation.</td>
2081
+ </tr>
2082
+ <tr>
2083
+ <td style="padding:15px">npm run adapter:findPath</td>
2084
+ <td style="padding:15px">Can be used to see if the adapter supports a particular API call.</td>
2085
+ </tr>
2086
+ <tr>
2087
+ <td style="padding:15px">npm run adapter:migrate</td>
2088
+ <td style="padding:15px">Provides an easier way to update your adapter after you download the migration zip from Itential DevSite.</td>
2089
+ </tr>
2090
+ <tr>
2091
+ <td style="padding:15px">npm run adapter:update</td>
2092
+ <td style="padding:15px">Provides an easier way to update your adapter after you download the update zip from Itential DevSite.</td>
2093
+ </tr>
2094
+ <tr>
2095
+ <td style="padding:15px">npm run adapter:revert</td>
2096
+ <td style="padding:15px">Allows you to revert after a migration or update if it resulted in issues.</td>
2097
+ </tr>
2098
+ <tr>
2099
+ <td style="padding:15px">npm run troubleshoot</td>
2100
+ <td style="padding:15px">Provides a way to troubleshoot the adapter - runs connectivity, healthcheck and basic get.</td>
2101
+ </tr>
2102
+ <tr>
2103
+ <td style="padding:15px">npm run connectivity</td>
2104
+ <td style="padding:15px">Provides a connectivity check to the Servicenow system.</td>
2105
+ </tr>
2106
+ <tr>
2107
+ <td style="padding:15px">npm run healthcheck</td>
2108
+ <td style="padding:15px">Checks whether the configured healthcheck call works to Servicenow.</td>
2109
+ </tr>
2110
+ <tr>
2111
+ <td style="padding:15px">npm run basicget</td>
2112
+ <td style="padding:15px">Checks whether the basic get calls works to Servicenow.</td>
2113
+ </tr>
2114
+ </table>
2115
+ <br>
2116
+
2117
+ ## Troubleshoot
2118
+
2119
+ Run `npm run troubleshoot` to start the interactive troubleshooting process. The command allows you to verify and update connection, authentication as well as healthcheck configuration. After that it will test these properties by sending HTTP request to the endpoint. If the tests pass, it will persist these changes into IAP.
2120
+
2121
+ You also have the option to run individual commands to perform specific test:
2122
+
2123
+ - `npm run healthcheck` will perform a healthcheck request of with current setting.
2124
+ - `npm run basicget` will perform some non-parameter GET request with current setting.
2125
+ - `npm run connectivity` will perform networking diagnostics of the adatper endpoint.
2126
+
2127
+ ### Connectivity Issues
2128
+
2129
+ 1. You can run the adapter troubleshooting script which will check connectivity, run the healthcheck and run basic get calls.
2130
+
2131
+ ```bash
2132
+ npm run troubleshoot
2133
+ ```
2134
+
2135
+ 2. Verify the adapter properties are set up correctly.
2136
+
2137
+ ```text
2138
+ Go into the Itential Platform GUI and verify/update the properties
2139
+ ```
2140
+
2141
+ 3. Verify there is connectivity between the Itential Platform Server and Azure_devops Server.
2142
+
2143
+ ```text
2144
+ ping the ip address of Azure_devops server
2145
+ try telnet to the ip address port of Azure_devops
2146
+ execute a curl command to the other system
2147
+ ```
2148
+
2149
+ 4. Verify the credentials provided for Azure_devops.
2150
+
2151
+ ```text
2152
+ login to Azure_devops using the provided credentials
2153
+ ```
2154
+
2155
+ 5. Verify the API of the call utilized for Azure_devops Healthcheck.
2156
+
2157
+ ```text
2158
+ Go into the Itential Platform GUI and verify/update the properties
2159
+ ```
2160
+
2161
+ ### Functional Issues
2162
+
2163
+ Adapter logs are located in `/var/log/pronghorn`. In older releases of the Itential Platform, there is a `pronghorn.log` file which contains logs for all of the Itential Platform. In newer versions, adapters can be configured to log into their own files.
2164
+
2165
+