LinkedIn
Copied!

Table of Contents

Dynamic system settings

Version:

Only available versions of this content are shown in the dropdown

Deployment Manager exposes a few Dynamic System Settings (DSS) to override the default behavior. See below for a list of configurations available to override the default behavior. All of these settings are optional and are not required by default. Carefully evaluate each configuration before configuring for your application.

Service connection timeout

All interactions within Deployment Manager happen through REST services, and the default time for these connections is 30 seconds. The DSS DMConnectorTimeOut is responsible for setting the timeout in milliseconds. The value is set to 30000 milliseconds (30 sec.) by default. This dynamic system setting value can be modified as required to affect the connection timeout when calling the Deployment Manager service. Note that this will cause longer interaction times for all connectors.

Owning ruleset PegaDeploymentManagerIntegrations
Purpose DMConnectorTimeOut
Value 30000

Application Mapping in External LDAP System

This DSS deploymentmanager/security/external_apps_mapping/enabled drives the source of the application mapping with the operator. If set to true, the applications available to a user is managed from the external authentication system (SSO or LDAP). If enabled. any changes made within Deployment Manager are overwritten with values from the authentication system on next operator log in.

Owning ruleset PegaDevopsShared
Purpose deploymentmanager/security/external_apps_mapping/enabled
Value False

Use JWT Grant Type

Merge actions are performed from the application instance of the developer. Currently, Deployment Manager uses client credentials to integrate with the orchestrator, however if there is a requirement to use JWT grant type, then the following dynamic system setting rule can be created and set to TRUE. This will enable tracking the initiator of a merge requests. In addition to this setting, the appropriate authentication profile and JWT client/server profiles must be updated on the candidate and orchestrator environments.

Owning ruleset PegaDevopsShared
Purpose deploymentmanager/security/use_jwt_grant_type/enabled
Value No value

Deployment History Maximum Size

The maximum count of deployments fetched for deployment history of a pipeline is currently set to 50. If you want to customize the default value, the following DSS can be edited and set to a new default value greater than 50. Note that the value set here will be applied for all pipelines and may potentially fetch large amounts of data if set to an arbitrarily large value. In addition to this you may have to increase the timeout setting to accommodate for the increased data, otherwise you may see blank deployment history.

Owning ruleset PegaDeploymentManagerCore
Purpose deploymentmanager/pipeline/maximum_deployments_to_show/size
Value 50

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.