CasC bundle management on the operations center HTTP API

The CasC bundle management on the operations center HTTP API allows users to view the availability patterns and tokens for all CasC bundles on the operations center. It also allows users to assign a bundle to a controller and regenerate tokens.

Authentication and authorization

To access the CasC bundle management on the operations center API you need an API authentication token and administrator access rights. See API authentication for more information.

Endpoints and methods

Endpoint Description Parameters Supported versions

GET ${JENKINS_URL}/casc-bundle/list

Lists all available CasC bundles on the operations center.

None.

2.249.2.3 and later

POST ${JENKINS_URL}/casc-bundle/regenerate-token

Regenerates the token and returns the new bundle information when successful.

Name: bundleId
- Parameter type: Query string parameter
- Data type: string
- Description: The name of the folder that contains the CasC bundle. For example, casc-bundle-java.

2.249.2.3 and later

POST ${JENKINS_URL}/casc-bundle/set-availability-pattern

Specifies the availability pattern, to define the path to controllers that can use the bundle.

Name: bundleId
- Parameter type: Query string parameter
- Data type: string
- Description: The name of the folder that contains the CasC bundle. For example, casc-bundle-java.
Name: regex
- Parameter type: Query string parameter
- Data type: string
- Description: The full path to one or more controllers that can use the bundle. This must be a regular expression and defines the bundles you can assign to a controller. For example, folder1/.* to use the bundle with any controller in the "folder1" folder.

2.289.2.2 and later

POST ${JENKINS_URL}/casc-bundle/set-global-availability-pattern-behavior

Specifies the default global availability pattern behavior.

Name: visibility
- Parameter type: Query string parameter
- Data type: string
- Description: When the parameter value is true, all CasC bundles that do not have a regex availability pattern defined can be used by any controller. This option provides more flexibility, but is less secure.

2.289.2.2 and later

POST ${JENKINS_URL}/casc-bundle/set-controller-to-bundle

Assigns a new controller path and returns the new bundle information when successful.

For this command to be successful, you must first define the availability pattern for the bundle by sending the /casc-bundle/set-availability-pattern or /casc-bundle/set-global-availability-pattern-behavior request.

Name: bundleId
- Parameter type: Query string parameter
- Data type: string
- Description: The name of the folder that contains the CasC bundle. For example, casc-bundle-java.
Name: controllerPath
- Parameter type: Query string parameter
- Data type: string
- Description: The full path of the controller item in the operations center. For example, folder1/controller1.

2.289.2.2 and later

POST ${JENKINS_URL}/casc-bundle/set-default-bundle

Specifies a default bundle that is pre-selected in the operations center controller configuration screen when setting up a new controller.

The default bundle is pre-selected for controllers that match the availability pattern of the default bundle. To set the availability pattern of the default bundle, you can use the /casc-bundle/set-availability-pattern or /casc-bundle/set-global-availability-pattern-behavior request.

Specifying a Default bundle does not assign the bundle to a controller. When setting up a new controller in the operations center, you must click Save or Apply from the controller configuration screen to assign the pre-selected bundle to the controller.

Name: bundleId
- Parameter type: Query string parameter
- Data type: string
- Description: The name of the folder that contains the CasC bundle. For example, casc-bundle-java.

2.289.2.2 and later

POST ${JENKINS_URL}/casc-bundle/set-master-to-bundle

Assigns a new controller path and returns the new bundle information when successful.

If you are using CloudBees CI 2.277.4.2 - 2.289.1.2, and you send the /casc-bundle/set-master-to-bundle endpoint, no bundles are available to assign to the controller. You must first sign in to the operations center as a user with the Administer permission, navigate to the Configuration as Code bundles screen, define the Availability pattern, and then issue the request to assign a bundle to a controller.

Name: bundleId
- Parameter type: Query string parameter
- Data type: string
- Description: The name of the folder that contains the CasC bundle. For example, casc-bundle-java.
Name: masterPath
- Parameter type: Query string parameter
- Data type: string
- Description: The full path of the controller item in the operations center. For example, folder1/controller1.

2.249.2.3 - 2.289.2.2

The /casc-bundle/set-master-to-bundle request has been deprecated in version 2.289.2.2 due to offensive terminology. The /casc-bundle/set-controller-to-bundle endpoint should be used for all new applications.

Request examples

In the request examples "admin" is the name of the user attempting to send the request and "https://my-operations-center.com/" is the operations center URL.

Table 2. Request examples
Endpoint	Request example
GET `/casc-bundle/list`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XGET "https://my-operation-center.com/casc-bundle/list"`
POST `/casc-bundle/regenerate-token`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/regenerate-token?bundleId=casc-bundle-java"`
POST `/casc-bundle/set-availability-pattern`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-availability-pattern?bundleId=casc-bundle-java&regex=folder1.*"`
POST `/casc-bundle/set-global-availability-pattern-behavior`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-global-availability-pattern-behavior?visibility=true"`
POST `/casc-bundle/set-controller-to-bundle`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-controller-to-bundle?bundleId=casc-bundle-java&controllerPath=folder1/controller1"`
POST `/casc-bundle/set-default-bundle`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-default-bundle?bundleId=casc-bundle-java"`
POST `/casc-bundle/set-master-to-bundle`	`curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-master-to-bundle?bundleId=casc-bundle-java&masterPath=folder1/controller1"`

Response examples

Response examples are formatted for better readability.

{
    "bundles":[
        {
            "linkFileContent":"url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
            "regex":"folder1/.*",
            "name":"casc-bundle-java",
            "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
            "token":""
        }
    ]
}

{
    "linkFileContent":"url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
    "token":""
}

{
    "controllers": [
        "folder1/controller1"
    ]
}

{
    "visibility": true
}

{
    "linkFileContent": "url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
    "token":""
}

{
    "linkFileContent": "url: \"http://localhost:8080/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url": "http://localhost:8080/config-bundle/casc-bundle-java",
    "token": ""
}

{
    "linkFileContent": "url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
    "token":""
}

Response model

Table 3. Response model
Element	Type	Description
bundles	array of objects	List of all bundles available on the operations center.
linkFileContent	string	Contains two entries in string format wrapped in quotes and separated by newline characters: url and token. The url is the bundle URL where the operations center exposes its content. The token is the access token for the bundle.
regex	string	The regex attribute is the full path to one or more controllers in the operations center that can use the bundle. This must be a regular expression. It defines the bundles you can assign to a controller. For example, `folder1/.*`.
name	string	The name is the name of the folder that contains the CasC bundle. For example, `casc-bundle-java`.
url	string	The url is the bundle URL where the operations center exposes its content.
token	string	The token is the access token for the bundle.
controllers	array of objects	List the full paths of all controllers that can use the bundle.

Status and error codes

Table 4. Status and error codes
Code	Description
200	Success
403	Not authorized. Administrator permission required.
404	The provided master path, endpoint, or method cannot be found.
500	Server error.

Examples for configuring a controller using CasC

Once the CasC bundle has been configured in the operations center, you can define an availability pattern to make the bundle available to controllers, assign the bundle to a controller, and specify a default bundle.

Send the GET /casc-bundle/list request to list all available CasC bundles on the operations center.

curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XGET "https://my-operation-center.com/casc-bundle/list"

In this example, there is one bundle named casc-bundle-java:

{
    "bundles":[
        {
            "linkFileContent":"url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
            "regex":"folder1/.*",
            "name":"casc-bundle-java",
            "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
            "token":""
        }
    ]
}

Define the availability pattern for the bundle. You have two options:
- Option 1: Send the POST /casc-bundle/set-availability-pattern command to define the path to the controllers that can use the bundle. For example:
  curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-availability-pattern?bundleId=casc-bundle-java&regex=folder1.*"
  If successful, a list of all controllers that can use the bundle is returned:
  { "controllers": [ "folder1/controller1" ] }
- Option 2: Send the POST /casc-bundle/set-global-availability-pattern-behavior command to define the default global availability pattern behavior for bundles that do not have an availability pattern defined. This option provides more flexibility, but is less secure. For example:
  curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-global-availability-pattern-behavior?visibility=true"
  If successful, the default global availability pattern behavior is returned:
  { "visibility": true }

Send the POST /casc-bundle/set-controller-to-bundle command to assign a bundle to a controller. For example:

curl --user "admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym" -XPOST "https://my-operation-center.com/casc-bundle/set-controller-to-bundle?bundleId=casc-bundle-java&controllerPath=folder1/controller1"

If successful, the bundle information is returned:

{
    "linkFileContent": "url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
    "token":""
}

Optionally, specify a default bundle to pre-select a bundle in the controller configuration screen when setting up a new controller. For example, to specify casc-bundle-java as the default bundle, send the POST /casc-bundle/set-default-bundle request:

java -jar jenkins-cli.jar -auth admin:rG57xFa2eFrCeWjG4NKU5QMJeW9TzfSkym -s https://my-operation-center.com/ -webSocket casc-bundle-set-default-bundle -b casc-bundle-java

If successful, the default bundle information is returned:

{
    "linkFileContent": "url: \"https://my-operation-center.com/config-bundle/casc-bundle-java\"\ntoken: \"\"\n",
    "regex":"folder1/.*",
    "name":"casc-bundle-java",
    "url":"https://my-operation-center.com/config-bundle/casc-bundle-java",
    "token":""
}

In August 2020, the Jenkins project voted to replace the term master with controller. We have taken a pragmatic approach to cleaning these up, ensuring the least amount of downstream impact as possible. CloudBees is committed to ensuring a culture and environment of inclusiveness and acceptance - this includes ensuring the changes are not just cosmetic ones, but pervasive. As this change happens, please note that the term master has been replaced through the latest versions of the CloudBees documentation with controller (as in managed controller, client controller, team controller) except when still used in the UI or in code.