Configure Callout URL

The CI JOBS screen is best viewed when the zoom setting is set to 80% on your chrome/firefox browser.

Overview

The callout URL lets you call another service from the ARM application via an HTTP request. For an HTTP callout to work correctly, all the HTTP callout parameters and the entities associated with the callout must be configured correctly.

Where can I find Configure Callout URL option?

A new section, i.e., Callout URL, is available for the following CI jobs:

• Deploy from Salesforce org

• Deploy from Salesforce org with a version control backup

• Deploy from version control

• Deploy Salesforce-DX (SFDX) source from version control

• Install an unlocked package from a version control branch

Configuring Callout URL

Callout URL

1. Select the Configure Callout URL checkbox under the Callout URL section.

2. Choose the Callout Type:

   1. Pre-Deployment: ARM will perform the HTTP request before the deployment begins, once the build is successful.

   2. Post-Deployment: By default, ARM will perform the HTTP request after the deployment is completed, regardless of whether it is successful. To run the HTTP request based on whether the deployment is a success or a failure, select the respective option:

      • On Success

      • On Failure

        
3. The callout URL method is selected as Post by default.

4. In the URL box, enter the target URL endpoint of the HTTP request.

5. Select the Authorization type:

   1. Basic: Authenticate the target URL via standard method-username and password

      
   2. Custom: Authenticate the connection via username: API Token

      
   3. OAuth: ARM supports the Client Credentials as a grant type for OAuth 2.0 authentication. To add an OAuth 2.0 provider, fill in the below details:

      • URL (required): OAuth 2.0 provider URL

      • Client ID (required): The client ID that your callout service uses to identify the ARM application

      • Client Secret (required): The client secret that your callout service uses to authenticate the identity of the ARM applicationThe Client Secret field is hidden during your current CI job editing, preventing you from updating the secret key. But you can insert a new secret key (if required).

      • Access token URL (required): The URL that the client uses to obtain an access token given an authorization code

      • Scope (optional): Specifies the level of access that the ARM application is requesting

      • Grant Type (required): The Grant Type is selected as Client Credentials by default

        
6. The Content-Type header describes the format in which the body of your request is being sent. For example, the body of your requests can be sent as JSON or XML.

   1. To send JSON in a request, use application/json and add your content in the field provided.

   2. To send XML in a request, use application/xml and add your content in the field provided.

      
7. To add a custom header, click on the Add Header button and enter the keys and their value. Multiple adding of keys and values are allowed.

Default headers is set as "Accept" :"application/json", "Content-Type":"application/json"

1. Click on Save.

Dynamic Parameters

Parameter	Description
{projectName}	Name of your CI Job
{buildNumber}	Build Number of your CI Job
{sforgName}	Name of your Salesforce Org

Note: You must specify values for dynamic parameters before executing the query, and the types of the specified values must match the expected types.

Viewing the Log Report

Callout Type: Pre-Deployment

You can view the detailed log report under the Build Log section.

Callout Type: Post-Deployment

View the detailed log report under the Deployment Log section.

Deployment Log

Deploy Log