Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

AnchorTopTop

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.

Info
titleBase URL for SCM Instance REST API

http://host:port/flexdeploy/rest/topology/integrations/scminstance

Table of Contents
maxLevel1

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

...

CVS 

...

File System

...

Git

...

Perforce

...

PVCS

...

Subversion

...

TFVC

...

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.

Info
titleAPI URL

http://host:port/flexdeploy/rest/topology/integrations/scminstance/{Id}

Parameters

...

Parameter

...

Required

...

Type

...

Description

...

Id

...

Response Codes

...

HTTP Code

...

Description

...

Example

If we had a SCM instance in our database with an Id of 11101 and had the following attributes

Code Block
themeEclipse
titleSCM Instance - 11101
{
   "name": "ScmName1",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "url"
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "user"
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "password"
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": "10000"
      }
   ],
   "type": "GIT",
   "description": "description",
   "code": "CODE1",
   "isActive": true
}

When we run a GET request at the following URL

http://host:port/flexdeploy/rest/topology/integrations/scminstance/11101

The GET request would return the  following JSON SCM instance object

Code Block
themeEclipse
titleSCM Instance GET Return JSON
{
   "name": "ScmName1",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "url"
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "user"
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "password"
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": "10000"
      }
   ],
   "type": "GIT",
   "description": "description",
   "code": "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
titleAPI URLs

http://host:port/flexdeploy/rest/topology/integrations/scminstance?

Append the following character sequences to the above URL to specify Query parameters.
Use '&' between successive query parameters: 

name={name}

code={code}

Examples:
To search by code only:

http://host:port/flexdeploy/rest/topology/integrations/scminstance?code={code}

To search by name only:

http://host:port/flexdeploy/rest/topology/integrations/scminstance?name={name}

To search by type and name:

http://host:port/flexdeploy/rest/topology/scminstance?type={type}&name={name}

Tip

The query parameters are not case sensitive. Searching by name=NAME is the same as searching by name=name.

Parameters

...

Parameter

...

Required

...

Type

...

Description

...

name

...

Response Codes

...

HTTP Code

...

Description

...

Example

...

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.

Include Page
REST V1 Authentication
REST V1 Authentication

Table of Contents
maxLevel2

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 NameProperty Key NameData TypeRequiredDescription
CVS URLFDCVS_URLStringYesURL to the CVS repository.
CVS UserFDCVS_PASSWORDStringYesCVS repository user.
CVS PasswordFDCVS_USERStringYesCVS repository password.

File System (FILE)

Property NameProperty Key NameData TypeRequiredDescription
File Repository RootFDFILE_REPO_ROOT_FOLDERStringYesLocation on the FlexDeploy server of the repository.

Git (GIT)

Property Display NameProperty Key NameData TypeRequiredDescription
Git URLFDGIT_URLStringYesURL to the Git repository.
Git UserFDGIT_USERStringYes/NoGit repository user.
Git PasswordFDGIT_PASSWORDStringYes/noGit repository password.
Git TimeoutFDGIT_TIMEOUTIntegerNoTimeout for Git command execution.

Perforce (PERF)

Property Display NameProperty Key NameData TypeRequiredDescription
Perforce HostFDPERF_HOSTStringYesHost of the Perforce repository.
Perforce PortFDPERF_PORTStringYesPort of the Perforce repository.
Perforce UserFDPERF_USERStringYesPerforce User to connect with.
Perforce User PasswordFDPERF_PASSWORDStringYesPerforce Password associated with Perforce User.
Perforce SSL ConnectionFDPERF_IS_SSLBooleanYesShould ssl be used connecting to the server.

PVCS (PVCS)

Property Display NameProperty Key NameData TypeRequiredDescription
PVCS Project DatabaseFDPVCS_PROJECT_DATABASEStringYesProject Database Name.
PVCS UserFDPVCS_USERStringYesPVCS user to access ProjectDatabases.
PVCS PasswordFDPVCS_PASSWORDStringYesPVCS password to access ProjectDatabases

Subversion (SVN)

Property Display NameProperty Key NameData TypeRequiredDescription
Subversion URLFDSVN_URLStringYesURL to the Subversion repository.
Subversion UserFDSVN_USERStringYesSubversion repository user.
Subversion PasswordFDSVN_PASSWORDStringYesSubversion repository password.
Subversion Authentication MethodsFDSVN_AUTH_METHODSStringNoOne or more subversion authentication methods. For example, Basic, Digest, Negotiate, NTLM.

TFVC (TFVC)

Property Display NameProperty Key NameData TypeRequiredDescription
TFVC URLFDTFVC_URLStringYesURL to the TFVC repository.
TFVC UserFDTFVC_USERStringYesTFVC repository user.
TFVC PasswordFDTFVC_USERStringYesTFVC 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
titleAPI URL

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id}

Request

Parameter
Required
Type
Description

Id

YesURLThis 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

HTTP Code
Description
200SCM instance was found and returned
400Bad request
401Authentication failure
403Authorization failure (no access to resource)
404SCM instance not found
500Unexpected 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
themeEclipse
titleSCM Instance - 11101
{
   "instanceId": 11101,
   "nameinstanceName": "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,
		 "10000credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "description",
   "codeinstanceCode": "CODE1",
   "isActive": true
}

When we run a GET request at the following URLhttp://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?code=code1&name=ScmName1/11101

The GET request would return the  following JSON SCM instance object

Code Block
themeEclipse
titleSCM Instance GET Return JSON
{
   "nameinstanceId": 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,
		 "10000credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "description",
   "codeinstanceCode": "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
titleAPI URLs

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance

Code Block
themeEclipse
titleSample POST JSON Request
{
   "name": "ScmName1",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "url"
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "user"
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "password"
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": "10000"
      }
   ],
   "type": "GIT",
   "description": "description",
   "code": "CODE1",
   "isActive": true
}

Parameters

...

Parameters

...

Required

...

Type

...

Description

...

Response Codes

...

HTTP Code

...

Description

...

?

Append the following character sequences to the above URL to specify Query parameters.
Use '&' between successive query parameters: 

instanceName={name}

instanceCode={code}

scmType={type}

isActive={boolean}

Examples:
To search by code only:

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?instanceCode={code}

To search by IsActive only:

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?isActive={boolean}

To search by name only:

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance?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 instanceName=NAME is the same as searching by instanceName=name.

Request

Parameter
Required
Type
Description

instanceName

NoQuery - String

This is a URL query parameter for the name which is used to query the SCM instances with.

Contains ignore case search

instanceCodeNoQuery - String

This is a URL query parameter for the code which is used to query the SCM instances with.

Equals ignore case search

scmTypeNoQuery - String

This is a URL query parameter for the type which is used to query the SCM instances with.

Equals ignore case search

isActiveNoQuery - BooleanReturns scm instances where isActive field matches parameter.

Include Page
REST V1 SCM Instance Response
REST V1 SCM Instance Response

Response Codes

HTTP Code
Description
200Search successful and results returned
400Bad request
401UnauthorizedAuthentication failure
404Instance not found
403Authorization failure (no access to resource)
500Unexpected internal server error

Example

If

the POST  request receives the following JSON test instance object,

we had a SCM instance in our database with an Id of 11101 and had the following attributes

Code Block
themeEclipse
titlePOST JSONSCM Instance - 11101
{
   "instanceId": 11101
   "nameinstanceName": "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,
		 "10000credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "description",
   "codeinstanceCode": "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 will then be created as a new row in the database.

Code Block
themeEclipse
titleSCM Instance
Post
GET Return JSON
{
   "
name
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
      }
   ],
   "
type
scmType": "GIT",
   "description": "description",
   "
code
instanceCode": "CODE1",
   "isActive": true
}
Back to Top

POST

PUT

This PUT POST service will update all attributes of create a new SCM instance with the same attributes as the given Id based on the attributes of a JSON object paramaters.

Info
titleAPI URL

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance

...

Code Block
themeEclipse
titleSample PUT JSON Request
{
   "name": "ScmName1",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "url"
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "user"
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "password"
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": "10000"
      }
   ],
   "type": "GIT",
   "description": "description",
   "code": "CODE1",
   "isActive": true
}

Parameters

...

Parameters

...

Required

...

Type

...

Description

...

Response Codes

...

HTTP Code

...

Description

...

Example

If we had a SCM instance in our database with an Id of 11101 and had the following attributes

Code Block
themeEclipse
titleSCM Instance PUT JSON
{ "name": "ScmName1", "properties": [ { "propertyName": "FDGIT_URL", "propertyValue": "url"

Parameters

Parameters
Required
Type
Description
IdYesURLThis is a URL parameter for the Id which is used to find and return an SCM instance with.
descriptionNoStringThis is the description that the SCM instance's description will be updated to.
isActiveYesBooleanThis is the isActive Boolean that the SCM instance's isActive Boolean will be updated to.
instanceCodeYesStringThis is the code that the SCM instance's code will be updated to.
propertiesYes/NoList<PropertyValue>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. More info on the PropertyValue object is included below.
instanceNameYesStringThis is the name that the SCM instance's name will be updated to.
scmTypeYesStringThis is the scm type of the SCM instance. 

PropertyValue

AttributesTypeDescription
propertyNameStringThis is the code of the property
propertyValueStringThis is the value of the property
credentialIdLongId of the credential associated with this property. Applicable only for encrypted properties.

Response Codes

HTTP Code
Description
201Instance was created successfully
400Bad request
401Authentication failure
403Authorization failure (no access to resource)
500Unexpected internal server error

Example

If the POST  request receives the following JSON test instance object,

Code Block
themeEclipse
titlePOST JSON
{
   "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",
   

...

When we run a PUT request at the following URL

http://host:port/flexdeploy/rest/topology/integrations/scminstance/11101

...

"description": "description",
   "instanceCode": "CODE1",
   "isActive": true
}

The following SCM instance object will then be created as a new row in the database.

Code Block
themeEclipse
titleSCM 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,
		 "credentialId": null
      }
   ],
   "scmType": "GIT",
   "description": "description",
   "instanceCode": "CODE1",
   "isActive": true
}

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.

Info
titleAPI URL

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id}

Request

Parameters
Required
Type
Description
IdYesURLThis is a URL parameter for the Id which is used to find and return an SCM instance with.
descriptionNoStringThis is the description that the SCM instance's description will be updated to.
isActiveYesBooleanThis is the isActive Boolean that the SCM instance's isActive Boolean will be updated to.
instanceCodeYesStringThis is the code that the SCM instance's code will be updated to.
propertiesYes/NoList<PropertyValue>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. More info on the PropertyValue object is included below.
instanceNameYesStringThis is the name that the SCM instance's name will be updated to.
scmTypeYesStringThis is the SCM type of the SCM instance.

PropertyValue

AttributesTypeDescription
propertyNameStringThis is the code of the property
propertyValueStringThis is the value of the property
credentialIdLongId 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

HTTP Code
Description
200SCM Instance was found and updated
400Bad request
401Authentication failure
403Authorization failure (no access to resource)
404SCM Instance not found
500Unexpected 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
themeEclipse
titleSCM Instance PUT Receive JSON
{
   "nameinstanceName": "ScmName2ScmName1",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "urlPUT""url",
		 "credentialId": null
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "user",
		 "userPUTcredentialId": null
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "passwordPUT"
password",
		 "credentialId": 46259
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": 10000,
		 "10001credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "descriptionPUTdescription",
   "codeinstanceCode": "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
themeEclipse
titleSCM Instance PUT Return Receive JSON
{
   "nameinstanceId": 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
      }
   ],
   "typescmType": "GIT",
   "description": "descriptionPUT",
   "codeinstanceCode": "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.

...

titleAPI URL

...

The PUT request would then update the SCM instance with Id 11101 and return the following JSON SCM instance object

Code Block
themeEclipse
title

...

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
titleAPI URL

http://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/{Id}

Request

Parameters
Required
Type
Description
IdYesURLThis is a URL parameter for the Id which is used to find and return an SCM instance with.
descriptionNoStringThis is the description that the SCM instance's description will be updated to.
isActiveNoBooleanThis is the isActive Boolean that the SCM instance's isActive Boolean will be updated to.
instanceCodeNoStringThis is the code that the SCM instance's code will be updated to.
propertiesNoList<PropertyValue>This is the list of Properties that will be updated in the SCM instance. Property values provided in input are updated, other values will be unchanged. More info on the PropertyValue object is included below.
instanceNameNoStringThis is the
code
name that the SCM instance's
code
name will be updated to.
properties
scmType
No
Yes
List<PropertyValuePojo>
StringThis is the
list of Properties that will be updated in
SCM type of the SCM instance.
The JSON object must have all of the properties of the SCM instance's type. nameNo

PropertyValue

AttributesTypeDescription
propertyNameStringThis is the code of the property
propertyValueStringThis is
the name that the SCM instance's name will be updated to.
the value of the property
credentialIdLongId 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

HTTP Code
Description
200SCM Instance was found and patched
400Bad request
401UnauthorizedAuthentication failure
403Authorization failure (no access to resource)
404SCM Instance not found
500Unexpected 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
themeEclipse
titleSCM Instance PATCH JSON
{
   "nameinstanceId": 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,
		 "10001credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "descriptionPUT",
   "codeinstanceCode": "CODE2",
   "isActive": true
}

When we run a PATCH request at the following URLhttp://host:port/flexdeploy/rest/v1/topology/integrations/scminstance/11101

And the PATCH request receives the following JSON SCM instance object,

Code Block
themeEclipse
titleSCM Instance Patch Receive JSON
{
   "nameinstanceName": null,
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "urlPatch"
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "",
		 "passwordPatchcredentialId": 15825
      },
   ],
   "typescmType": "GIT",
   "description": null,
   "codeinstanceCode": "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
themeEclipse
titleSCM Instance PATCH Return JSON
{
   "nameinstanceId": 11101,
   "instanceName": "ScmName2",
   "properties":    [
            {
         "propertyName": "FDGIT_URL",
         "propertyValue": "urlPatch",
		 "credentialId": null
      },
            {
         "propertyName": "FDGIT_USER",
         "propertyValue": "userPUT",
		 "credentialId": null
      },
            {
         "propertyName": "FDGIT_PASSWORD",
         "propertyValue": "passwordPatch*****",
		 "credentialId": 15825
      },
            {
         "propertyName": "FDGIT_TIMEOUT",
         "propertyValue": "10001",
		 "credentialId": null
      }
   ],
   "typescmType": "GIT",
   "description": "descriptionPUT",
   "codeinstanceCode": "CODE3",
   "isActive": true
}
Back to Top