Integrate a remote source code repository on CloudBolt Documentation

GitHub App authentication

Mon, 01 Jan 0001 00:00:00 +0000

A GitHub source code repository connection authenticates with either a Personal Access Token (PAT) or a GitHub App. Both methods support reading (auto-import) and pushing, work with GitHub Cloud and self-hosted GitHub Enterprise Server, and are selected per connection. The same repository can therefore authenticate differently in different Cloud Management Platform (CMP) environments.

Personal Access Token	GitHub App
A personal identity. The connection stores a read token, and each user pushes with their own token.	A non-personal, organization-owned identity that keeps working when people change teams or leave.
Best for development environments, where users author content and push it under their own GitHub identity.	Best for staging, QA, and production, as it refreshes promoted content without relying on an individual’s token.

In a typical promotion workflow, developers connect with PATs and push blueprints, actions, and other content to the repository. Each higher-level environment connects to the same repository with a GitHub App and refreshes the promoted content.

Blueprints as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a blueprint is linked to a repository, you can push it, preview the changes, and later refresh the blueprint from the repository. You can also create a blueprint from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a blueprint

Open the blueprint from the Catalog, then select its repository tab. The tab is named Repository until the blueprint is linked to a repository; then it is named GitHub or GitLab.

Continuous Infrastructure Testing as code

Mon, 01 Jan 0001 00:00:00 +0000

A test that runs an action can be pushed to a repository and refreshed from it later, and you can add a test from an action already in a repository. Tests of other kinds have no repository tab. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a test

Open the test from Admin > Continuous Infrastructure Testing, then select the Repository tab. Unlike other content types, this tab keeps the same name regardless of which provider the repository belongs to.

Flow control actions as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a flow control action is linked to a repository, you can push it, preview the changes, and later refresh the action from the repository. You can also create an action from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a flow control action

Open the action from Admin > Flow Control Actions, then select its repository tab. The tab is named Repository until the action is linked to a repository; then it is named GitHub or GitLab.

Inbound webhooks as code

Mon, 01 Jan 0001 00:00:00 +0000

Once an inbound webhook is linked to a repository, you can push it, preview the changes, and later refresh the webhook from the repository. You can also create a webhook from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh an inbound webhook

Open the webhook from Admin > Inbound Web Hooks, then select its repository tab. The tab is named Repository until the webhook is linked to a repository; then it is named GitHub or GitLab.

Orchestration actions as code

Mon, 01 Jan 0001 00:00:00 +0000

Once an orchestration action is linked to a repository, you can push it, preview the changes, and later refresh the action from the repository. You can also create an action from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh an orchestration action

Open the action from Admin > Orchestration Actions, then select its repository tab. The tab is named Repository until the action is linked to a repository; then it is named GitHub or GitLab.

Recurring jobs as code

Mon, 01 Jan 0001 00:00:00 +0000

A recurring job that runs an action can be pushed to a repository and refreshed from it later, and you can add a recurring job from an action already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a recurring job

Open the job from Admin > Recurring Jobs, then select its repository tab. The tab is named Repository until the job is linked to a repository; then it is named GitHub or GitLab.

Resource actions as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a resource action is linked to a repository, you can push it, preview the changes, and later refresh the action from the repository. You can also create an action from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a resource action

Open the action from Admin > Resource Actions, then select its repository tab. The tab is named Repository until the action is linked to a repository; then it is named GitHub or GitLab.

Server actions as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a server action is linked to a repository, you can push it, preview the changes, and later refresh the action from the repository. You can also create an action from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a server action

Open the action from Admin > Server Actions, then select its repository tab. The tab is named Repository until the action is linked to a repository; then it is named GitHub or GitLab.

Shared modules as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a shared module is linked to a repository, you can push it, preview the changes, and later refresh the module from the repository. You can also create a module from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a shared module

Open the module from Admin > Shared Modules, then select its repository tab. The tab is named Repository until the module is linked to a repository; then it is named GitHub or GitLab.

UI extensions as code

Mon, 01 Jan 0001 00:00:00 +0000

Once a UI extension is linked to a repository, you can push it, preview the changes, and later refresh the extension from the repository. You can also add an extension package from one already in a repository. This requires a repository linked to Cloud Management Platform (CMP) and repository credentials on your profile so commits are attributed to you. See Integrate a remote source code repository.

Push and refresh a UI extension

Go to Admin > Manage UI Extensions, open the extension, and select the Repository tab. Unlike other content types, this tab keeps the same name regardless of which provider the repository belongs to.