- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
Private actions allow your Datadog workflows and apps to interact with services hosted on your private network without exposing your services to the public internet. To use private actions, you must use Docker to install a private action runner on a host in your network and pair the runner with a Datadog Connection. For more information on setting up a runner and pairing it with a connection, see Private Actions for Workflows or Private Actions for App Builder.
Some private actions, such as Jenkins and PostgreSQL, require credentials to function. To configure credentials for a private action, you must:
/etc/dd-action-runner/creds/jenkins_creds.json
.The PostgreSQL connection requires a PostgreSQL Connection URI credential.
This example uses the URI postgres://usr:password@example_host:5432/example_db
. For information on constructing a PostgreSQL connection URI, see the official PostgreSQL documentation.
/etc/dd-action-runner/creds/creds.pgpass
{
"auth_type": "Token Auth",
"credentials": [
{
"tokenName": "connectionUri",
"tokenValue": "postgres://usr:password@example_host:5432/example_db"
}
]
}
In the runner’s connection, specify the location of the credential file on the private action runner’s container. In this example, the credential is stored at /etc/dd-action-runner/creds/creds.pgpass
on the runner.
Jenkins connections require three credentials:
You can include all credentials in a single file or store each credential in a separate file.
Single file example
In the runner’s connection, specify the location of the credential file on the private action runner’s container. In this example, all three credentials are stored in a single file. Replace USERNAME
, TOKEN
, and DOMAIN
with your username, token, and domain.
/etc/dd-action-runner/creds/jenkins_creds.json
{
"auth_type": "Token Auth",
"credentials": [
{
"username": "USERNAME",
"token": "TOKEN",
"domain": "DOMAIN"
}
]
}
In the runner’s connection, specify the location of the credential file on the private action runner’s container. Your Jenkins connection points to the same path for all credentials. In this example, the credential file is stored at /etc/dd-action-runner/creds/jenkins_creds.json
on the runner.
Multiple file example
In this example, each Jenkins credential is stored in a separate file.
For the username credential, replace USERNAME
with your username.
/etc/dd-action-runner/creds/jenkins_username.json
{
"auth_type": "Token Auth",
"credentials": [
{
"username": "USERNAME"
}
]
}
For the token credential, replace TOKEN
with your token.
/etc/dd-action-runner/creds/jenkins_token.json
{
"auth_type": "Token Auth",
"credentials": [
{
"token": "TOKEN"
}
]
}
For the domain credential, replace DOMAIN
with your domain.
/etc/dd-action-runner/creds/jenkins_domain.json
{
"auth_type": "Token Auth",
"credentials": [
{
"domain": "DOMAIN"
}
]
}
In the runner’s connection, specify the location of the credential file on the private action runner’s container. Your Jenkins connection points to the path to each credential. In this example, the credential files are stored at the following locations on the runner:
/etc/dd-action-runner/creds/jenkins_username.json
/etc/dd-action-runner/creds/jenkins_token.json
/etc/dd-action-runner/creds/jenkins_domain.json
Basic authentication for the HTTP connection requires a credential file with a username and a password.
Replace USERNAME
and PASSWORD
with your username and password.
/etc/dd-action-runner/creds/http_creds.json
{
"auth_type": "Basic Auth",
"credentials": [
{
"username": "USERNAME",
"password": "PASSWORD"
}
]
}
In the runner’s connection, specify the location of the credential file on the private action runner’s container. In this example, the credential file is stored at /etc/dd-action-runner/creds/http_creds.json
on the runner.
Token authentication for the HTTP connection requires a credential file with an array of token names and values.
The example below includes two tokens named TOKEN1
and TOKEN2
. Replace the example token names and values with your token names and values.
/etc/dd-action-runner/creds/http_creds.json
{
"auth_type": "Token Auth",
"credentials": [
{
"tokenName": "TOKEN1",
"tokenValue": "VALUE1"
},
{
"tokenName": "TOKEN2",
"tokenValue": "VALUE2"
}
]
}
In the runner’s connection, specify the location of the credential file on the private action runner’s container. In this example, the credential file is stored at /etc/dd-action-runner/creds/http_creds.json
on the runner.