Anchor |
---|
Top | Top | SCM Instances can be accessed and modified through this API using four services: GET, POST, PUT, and PATCH. These four services SCM Instances can be accessed and modified through this API using four services: GET, POST, PUT, and PATCH. These four services allow for the retrieval, creation, complete update, and partial update of SCM Instances....
...
title | Base URL for SCM Instance REST API |
---|
...
http://host:port/flexdeploy/rest/topology/integrations/scminstance
| REST V1 Authentication |
---|
| REST V1 Authentication |
---|
|
Each function returns a JSON test instance object. The test SCM instance Object is an object that has these attributes,
...
Currently there are 8 different source control management types that are supported in Flex Deploy.
ClearCaseUCM
Currently there are 8 different source control management types that are supported in Flex Deploy. The scmType value is shown after the name of each.
CVS (CVS)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
CVS URL | FDCVS_URL | String | Yes | URL to the CVS repository. |
CVS User | FDCVS_PASSWORD | String | Yes | CVS repository user. |
CVS Password | FDCVS_USER | String | Yes | CVS repository password. |
File System (FILE)
Property Name | Property Key Name | Data Type | Required | Description |
---|
File Repository Root | FDFILE_REPO_ROOT_FOLDER | String | Yes | Location on the FlexDeploy server of the repository. |
Git (GIT)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
ClearCaseUCM FDCCUCM of ClearCase ServerClearCaseUCM FDCCUCMClearCase User to connect withClearCaseUCM FDCCUCMClearCase Password for connecting user. | CVS /no | Git repository password. |
Git Timeout | FDGIT_TIMEOUT | Integer | No | Timeout for Git command execution. |
Perforce (PERF)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
CVS URLFDCVSURLURL to CVS CVS UserFDCVSPASSWORDCVS Port of the Perforce repository |
userCVS PasswordFDCVSCVS repository passwordPerforce User to connect with. |
File System
Property Name | Property Key Name | Data Type | Required | Description |
---|
File Repository Root | FDFILE_REPO_ROOT_FOLDER | String | Yes | Location on the FlexDeploy server of the repository. |
GitPerforce User Password | FDPERF_PASSWORD | String | Yes | Perforce Password associated with Perforce User. |
Perforce SSL Connection | FDPERF_IS_SSL | Boolean | Yes | Should ssl be used connecting to the server. |
PVCS (PVCS)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
Git URL | FDGIT_URLPVCS Project Database | FDPVCS_PROJECT_DATABASE | String | Yes |
URL to the Git repositoryGit FDGIT/NoGit repository PVCS user to access ProjectDatabases. |
Git FDGIT/noGit repository password. | Git Timeout | FDGIT_TIMEOUT | Integer | No | Timeout for Git command execution. |
Perforce
PVCS password to access ProjectDatabases |
Subversion (SVN)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
Perforce HostFDPERFHOSTHost of Perforce Perforce PortFDPERFPORTPort of the Perforce Subversion repository user. |
Perforce UserFDPERFUSERFDPERF_PASSWORDPerforce User to connect with. | Perforce User Password | Subversion repository password. |
Subversion Authentication Methods | FDSVN_AUTH_METHODS | String |
Yes | Perforce Password associated with Perforce User. | Perforce SSL Connection | FDPERF_IS_SSL | Boolean | Yes | Should ssl be used connecting to the server. |
PVCSNo | One or more subversion authentication methods. For example, Basic, Digest, Negotiate, NTLM. |
TFVC (TFVC)
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
PVCS Project Database | FDPVCS_PROJECT_DATABASETFVC URL | FDTFVC_URL | String | Yes |
Project Database NameURL to the TFVC repository. |
PVCS FDPVCSPVCS to access ProjectDatabasesPVCS FDPVCSPASSWORDPVCS password to access ProjectDatabases | Subversion
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
Subversion URL | FDSVN_URL | String | Yes | URL to the Subversion repository. |
Subversion User | FDSVN_USER | String | Yes | Subversion repository user. |
Subversion Password | FDSVN_PASSWORD | String | Yes | Subversion repository password. |
Subversion Authentication Methods | FDSVN_AUTH_METHODS | String | No | One or more subversion authentication methods. For example, Basic, Digest, Negotiate, NTLM. |
TFVC
Property Display Name | Property Key Name | Data Type | Required | Description |
---|
TFVC URL | FDTFVC_URL | String | Yes | URL to the TFVC repository. |
TFVC User | FDTFVC_USER | String | Yes | TFVC repository user. |
TFVC Password | FDTFVC_USER | String | Yes | TFVC repository password. |
Back to Top
GET
There are two implementations of GET. One will find a SCM instance with the given Id and return the JSON representation of the SCM instance. The other will find a list of SCM instances matching the parameters supplied to it.
GET (Using Id)
This GET service will find a SCM instance with the given Id and return the JSON representation of the object.
Parameters
Id | Yes | URL | This is a URL parameter for the Id which is used to find and return a SCM instance with. |
Response Codes
200 | SCM instance was found and returned |
400 | Bad request |
401 | Unauthorized |
500 | Unexpected internal server error |
Example
If we had a SCM instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance - 11101 |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
TFVC repository password. |
GET
There are two implementations of GET. One will find a SCM instance with the given Id and return the JSON representation of the SCM instance. The other will find a list of SCM instances matching the parameters supplied to it.
GET (Using Id)
This GET service will find a SCM instance with the given Id and return the JSON representation of the object.
Info |
---|
|
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id} |
Request
Id | Yes | URL | This is a URL parameter for the Id which is used to find and return a SCM instance with. |
Include Page |
---|
| REST V1 SCM Instance Response |
---|
| REST V1 SCM Instance Response |
---|
|
Response Codes
200 | SCM instance was found and returned |
400 | Bad request |
401 | Authentication failure |
403 | Authorization failure (no access to resource) |
404 | SCM instance not found |
500 | Unexpected internal server error |
Example
If we had a SCM instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance - 11101 |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"credentialId": null
},
{
"propertyName": "FDGIT_URLUSER",
"propertyValue": "url"
},
{
"propertyName": "FDGIT_USER",user",
"credentialId": null
"propertyValue": "user"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": 10000,
"10000credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
When we run a GET request at the following URL: http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/11101
The GET request would return the following JSON SCM instance object
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance GET Return JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password"
*****",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"
10000,
"credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
Back to Top
GET (Using Query Parameters)
This GET service will find a SCM instance by querying based on a name, code, and/or type of the SCM and return the JSON representations of the objects. If no query parameters are given this request will return the entire list of SCM instances.
Info |
---|
|
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance? Append the following character sequences to the above URL to specify Query parameters.Use '&' between successive query parameters: instancenameinstanceName={name} instancecodeinstanceCode={code} scmtypescmType={type} isActive={boolean} Examples:To search by code only:http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?instancecodeinstanceCode={code} To search by name IsActive only:http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?instancenameisActive={nameboolean} To search by type and name only:http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?scmtypeinstanceName={type}&instancename={name} To search by type and name:http://host:port/flexdeploy/rest/v1/topology/scminstance?scmType={type}&instanceName={name} |
Tip |
---|
The query parameters are not case sensitive. Searching by nameinstanceName=NAME is the same as searching by nameinstanceName=name. |
...
Request
instancenameURL(query)Query - String | This is a URL query parameter for the name which is used to query the SCM instances with. Contains ignore case search |
instancecodeURL(query)Query - String | This is a URL query parameter for the code which is used to query the SCM instances with. Equals ignore case search |
scmtypeURL(query200 | SCM Instances were found and Query - String | This is a URL query parameter for the type which is used to query the SCM instances with. |
Response Codes
Equals ignore case search |
isActive | No | Query - Boolean | Returns scm instances where isActive field matches parameter. |
Include Page |
---|
| REST V1 SCM Instance Response |
---|
| REST V1 SCM Instance Response |
---|
|
Response Codes
200 | Search successful and results returned |
400 | Bad request |
401Unauthorized | Authentication failure |
403 | Authorization failure (no access to resource) |
500 | Unexpected internal server error |
Example
If we had a SCM instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance - 11101 |
---|
|
{
"instanceId": 11101
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000",
"credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
When we run a GET request at the following URL
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?code=code1&name=ScmName1
The GET request would return the following JSON SCM instance object
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance GET Return JSON |
---|
|
{
"instanceId": 11101
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"10000,
"credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
...
This POST service will create a new SCM instance with the same attributes as the given JSON object.
Info |
---|
|
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance |
Code Block |
---|
theme | Eclipse |
---|
title | Sample POST JSON Request |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url"
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password"
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"
Parameters
PropertyValue
Attributes | Type | Description |
---|
propertyName | String | This is the code of the property |
propertyValue | String | This is the value of the property |
credentialId | Long | Id of the credential associated with this property. Applicable only for encrypted properties. |
Response Codes
201 | Instance was created successfully |
400 | Bad request |
401 | Authentication failure |
403 | Authorization failure (no access to resource) |
500 | Unexpected internal server error |
Example
If the POST request receives the following JSON test instance object,
Code Block |
---|
theme | Eclipse |
---|
title | POST JSON |
---|
|
{
"instanceName": "ScmName1",
"properties": [
|
...
...
...
"propertyName": "FDGIT_URL",
" |
...
...
"url",
"credentialId": null
},
|
...
...
...
...
Parameters
Id | Yes | URL | This is a URL parameter for the Id which is used to find and return an SCM instance with. |
description | No | String | This is the description that the SCM instance's description will be updated to. |
isActive | Yes | Boolean | This is the isActive Boolean that the SCM instance's isActive Boolean will be updated to. |
instanceCode | Yes | String | This is the code that the SCM instance's code will be updated to. |
properties | Yes/No | List<PropertyValuePojo> | This is the list of Properties that will be updated in the SCM instance. The JSON object must have all of the properties of the SCM instance's type. |
instanceName | Yes | String | This is the name that the SCM instance's name will be updated to. |
instanceId | No | Long | This is the unique Id of the SCM instance. The SCM Instance will not be updated from this. |
scmtype | Yes | String | This is the scm type of the SCM instance. |
Response Codes
201 | Instance was created successfully |
400 | Bad request |
401 | Unauthorized |
404 | Instance not found |
500 | Unexpected internal server error |
Example
If the POST request receives the following JSON test instance object,
Code Block |
---|
theme | Eclipse |
---|
title | POST JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1", "user",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": 10000,
"credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
The following SCM instance object will then be created as a new row in the database.
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance Post Return JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": |
"10000"10000,
"credentialId": null
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
The following SCM instance object will then be created as a new row in the database.
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance Post Return JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url"
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password"
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
Back to Top
PUT
This PUT service will update all attributes of a SCM instance with the given Id based on the attributes of a JSON object paramaters.
Code Block |
---|
theme | Eclipse |
---|
title | Sample PUT JSON Request |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url"
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password"
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
Parameters
...
...
...
...
...
Response Codes
...
...
...
Example
If we had a SCM instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance PUT JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url"
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "password"
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10000"
}
],
"scmType": "GIT",
"description": "description",
"instanceCode": "CODE1",
"isActive": true
} |
When we run a PUT request at the following URL
http://host:port/flexdeploy/rest/topology/integrations/scminstance/11101
...
This PUT service will update all attributes of a SCM instance with the given Id based on the attributes of a JSON object paramaters.
Info |
---|
|
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id} |
Request
PropertyValue
Attributes | Type | Description |
---|
propertyName | String | This is the code of the property |
propertyValue | String | This is the value of the property |
credentialId | Long | Id of the credential associated with this property. Applicable only for encrypted properties. |
Include Page |
---|
| REST V1 SCM Instance Response |
---|
| REST V1 SCM Instance Response |
---|
|
Response Codes
200 | SCM Instance was found and updated |
400 | Bad request |
401 | Authentication failure |
403 | Authorization failure (no access to resource) |
404 | SCM Instance not found |
500 | Unexpected internal server error |
Example
If we had a SCM instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance PUT Receive JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName2ScmName1",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "url",
"propertyValuecredentialId": "urlPUT"null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "user",
"userPUTcredentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "passwordPUT"
password",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10001"
10000,
"credentialId": null
}
],
"scmType": "GIT",
"description": "descriptionPUTdescription",
"instanceCode": "CODE2CODE1",
"isActive": true
} |
The When we run a PUT request would then update the SCM instance with Id 11101 and return the following JSON SCM instance objectat the following URL: http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/11101
And the PUT request recieves the following JSON SCM instace object,
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance PUT Return Receive JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName2",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "urlPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "userPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "passwordPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10001"10001,
"credentialId": null
}
],
"scmType": "GIT",
"description": "descriptionPUT",
"instanceCode": "CODE2",
"isActive": true
} |
Back to Top
PATCH
This PATCH service will update an existing SCM instance with the information passed through a JSON object. If an attribute of the JSON is null it will not be updated in the SCM instance.
...
...
The PUT request would then update the SCM instance with Id 11101 and return the following JSON SCM instance object
...
SCM Instance PUT Return JSON |
|
...
|
{
"instanceId": 11101,
"instanceName": " |
...
ScmName2",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "urlPUT",
" |
...
credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "userPUT",
" |
...
credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "*****",
"credentialId": |
...
46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": 10001,
" |
...
credentialId": null
}
],
"scmType": "GIT",
"description": " |
...
descriptionPUT",
"instanceCode": " |
...
CODE2",
"isActive": true
} |
...
PATCH
This PATCH service will update an existing SCM instance with the information passed through a JSON object. If an attribute of the JSON is null it will not be updated in the SCM instance.
Info |
---|
|
http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id} |
Request
List<PropertyValuePojo>. The JSON object must have all of the properties of the SCM instance's type. instanceIdNoLong unique Id The SCM Instance will not be updated from this.
scmtype | Yes | String | This is the SCM type of the SCM instance.PropertyValue
Attributes | Type | Description |
---|
propertyName | String | This is the code of the property |
propertyValue | String | This is the value of the property |
credentialId | Long | Id of the credential associated with this property. Applicable only for encrypted properties. |
Include Page |
---|
| REST V1 SCM Instance Response |
---|
| REST V1 SCM Instance Response |
---|
|
Response Codes
200 | SCM Instance was found and patched |
400 | Bad request |
401Unauthorized | Authentication failure |
403 | Authorization failure (no access to resource) |
404 | SCM Instance not found |
500 | Unexpected internal server error |
Example
If we had an test instance in our database with an Id of 11101 and had the following attributes
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance PATCH JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName2",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "urlPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "userPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "passwordPUT",
"credentialId": 46259
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": 10001,
"propertyValuecredentialId": "10001"null
}
],
"scmType": "GIT",
"description": "descriptionPUT",
"instanceCode": "CODE2",
"isActive": true
} |
When we run a PATCH request at the following URL: http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/11101
And the PATCH request receives the following JSON SCM instance object,
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance Patch Receive JSON |
---|
|
{
"instanceId": 11101,
"instanceName": null,
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "urlPatch"
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "",
"passwordPatchcredentialId": 15825
},
],
"scmType": "GIT",
"description": null,
"instanceCode": "CODE3",
"isActive": true
} |
The PATCH request would then update the SCM instance with Id 11101 and return the the following JSON SCM instance object
Code Block |
---|
theme | Eclipse |
---|
title | SCM Instance PATCH Return JSON |
---|
|
{
"instanceId": 11101,
"instanceName": "ScmName2",
"properties": [
{
"propertyName": "FDGIT_URL",
"propertyValue": "urlPatch",
"credentialId": null
},
{
"propertyName": "FDGIT_USER",
"propertyValue": "userPUT",
"credentialId": null
},
{
"propertyName": "FDGIT_PASSWORD",
"propertyValue": "*****",
"passwordPatchcredentialId": 15825
},
{
"propertyName": "FDGIT_TIMEOUT",
"propertyValue": "10001",
"credentialId": null
}
],
"scmType": "GIT",
"description": "descriptionPUT",
"instanceCode": "CODE3",
"isActive": true
} |
Back to Top