...
A subscription to the Git Integration for GHES
Anchor | ||||
---|---|---|---|---|
|
A GHES administrator must create an App in GHES to enable interaction between GHES and SnapLogic. In addition to the App, the network must be configured to allow communication between GHES and the SnapLogic control plane.
...
Anchor | ||||
---|---|---|---|---|
|
The steps outlined in this section are subject to change. If necessary, use the latest GitHub documentation on creating Apps for the general procedures.
...
The client secret and the
.pem
file that contains the Private Key.The Public Link
The Client ID
The App ID
Anchor | ||||
---|---|---|---|---|
|
A network administrator must perform the following to enable communication between GHES and SnapLogic:
...
Usage | Endpoint URL |
List app installations accessible to the user access token |
|
List repositories accessible to the user access token |
|
Get a single reference |
|
Pull |
|
Create Commit |
|
Get Commit |
|
Get Repo Contents |
|
Get a Blob |
|
Create a blob |
|
List Repo Tags |
|
Create New File |
|
Create Git Tree |
|
Anchor | ||||
---|---|---|---|---|
|
As a SnapLogic Org admin, configure GHES in Manager as follows:
...
Next, individual SnapLogic users will need to authorize SnapLogic to interact with GHES.