TeamCity Sync

Learn how to configure a TeamCity Sync for Infisical.

Prerequisites:

• Set up and add secrets to Infisical Cloud
• Create a TeamCity Connection with the required Secret Sync permissions

Infisical UI

1. Navigate to Project > Integrations and select the Secret Syncs tab. Click on the Add Sync button.

2. Select the TeamCity option.

3. Configure the Source from where secrets should be retrieved, then click Next.

   • Environment: The project environment to retrieve secrets from.
   • Secret Path: The folder path to retrieve secrets from.

If you need to sync secrets from multiple folder locations, check out secret imports.

4. Configure the Destination to where secrets should be deployed, then click Next.

   • TeamCity Connection: The TeamCity Connection to authenticate with.
   • Project: The TeamCity project to sync secrets to.
   • Build Configuration: The build configuration to sync secrets to.
   Not including a Build Configuration will sync secrets to the project.

5. Configure the Sync Options to specify how secrets should be synced, then click Next.

   • Initial Sync Behavior: Determines how Infisical should resolve the initial sync.

     • Overwrite Destination Secrets: Removes any secrets at the destination endpoint not present in Infisical.
     • Import Secrets (Prioritize Infisical): Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over TeamCity when keys conflict.
     • Import Secrets (Prioritize TeamCity): Imports secrets from the destination endpoint before syncing, prioritizing values from TeamCity over Infisical when keys conflict.
     Infisical only syncs secrets from within the target scope; inherited secrets will not be imported.

   • Key Schema: Template that determines how secret names are transformed when syncing, using {{secretKey}} as a placeholder for the original secret name and {{environment}} for the environment.

   We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.

   • Auto-Sync Enabled: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
   • Disable Secret Deletion: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.

6. Configure the Details of your TeamCity Sync, then click Next.

   • Name: The name of your sync. Must be slug-friendly.
   • Description: An optional description for your sync.

7. Review your TeamCity Sync configuration, then click Create Sync.

8. If enabled, your TeamCity Sync will begin syncing your secrets to the destination endpoint.

1. Navigate to Project > Integrations and select the Secret Syncs tab. Click on the Add Sync button.

2. Select the TeamCity option.

3. Configure the Source from where secrets should be retrieved, then click Next.

   • Environment: The project environment to retrieve secrets from.
   • Secret Path: The folder path to retrieve secrets from.

If you need to sync secrets from multiple folder locations, check out secret imports.

4. Configure the Destination to where secrets should be deployed, then click Next.

   • TeamCity Connection: The TeamCity Connection to authenticate with.
   • Project: The TeamCity project to sync secrets to.
   • Build Configuration: The build configuration to sync secrets to.
   Not including a Build Configuration will sync secrets to the project.

5. Configure the Sync Options to specify how secrets should be synced, then click Next.

   • Initial Sync Behavior: Determines how Infisical should resolve the initial sync.

     • Overwrite Destination Secrets: Removes any secrets at the destination endpoint not present in Infisical.
     • Import Secrets (Prioritize Infisical): Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over TeamCity when keys conflict.
     • Import Secrets (Prioritize TeamCity): Imports secrets from the destination endpoint before syncing, prioritizing values from TeamCity over Infisical when keys conflict.
     Infisical only syncs secrets from within the target scope; inherited secrets will not be imported.

   • Key Schema: Template that determines how secret names are transformed when syncing, using {{secretKey}} as a placeholder for the original secret name and {{environment}} for the environment.

   We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.

   • Auto-Sync Enabled: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
   • Disable Secret Deletion: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.

6. Configure the Details of your TeamCity Sync, then click Next.

   • Name: The name of your sync. Must be slug-friendly.
   • Description: An optional description for your sync.

7. Review your TeamCity Sync configuration, then click Create Sync.

8. If enabled, your TeamCity Sync will begin syncing your secrets to the destination endpoint.

To create a TeamCity Sync, make an API request to the Create TeamCity Sync API endpoint.

Sample request

Request

curl    --request POST \
--url https://app.infisical.com/api/v1/secret-syncs/teamcity \
--header 'Content-Type: application/json' \
--data '{
    "name": "my-teamcity-sync",
    "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "description": "an example sync",
    "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "environment": "dev",
    "secretPath": "/my-secrets",
    "isEnabled": true,
    "syncOptions": {
        "initialSyncBehavior": "overwrite-destination"
    },
    "destinationConfig": {
        "project": "TestProject",
        "buildConfig": "TestBuildConfig"
    }
}'

The Project and Build Config parameters must use project and build configuration IDs, not their names.

Sample response

Response

{
    "secretSync": {
        "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "name": "my-teamcity-sync",
        "description": "an example sync",
        "isEnabled": true,
        "version": 1,
        "folderId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "createdAt": "2023-11-07T05:31:56Z",
        "updatedAt": "2023-11-07T05:31:56Z",
        "syncStatus": "succeeded",
        "lastSyncJobId": "123",
        "lastSyncMessage": null,
        "lastSyncedAt": "2023-11-07T05:31:56Z",
        "importStatus": null,
        "lastImportJobId": null,
        "lastImportMessage": null,
        "lastImportedAt": null,
        "removeStatus": null,
        "lastRemoveJobId": null,
        "lastRemoveMessage": null,
        "lastRemovedAt": null,
        "syncOptions": {
            "initialSyncBehavior": "overwrite-destination"
        },
        "projectId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "connection": {
            "app": "teamcity",
            "name": "my-teamcity-connection",
            "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
        },
        "environment": {
            "slug": "dev",
            "name": "Development",
            "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
        },
        "folder": {
            "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
            "path": "/my-secrets"
        },
        "destination": "teamcity",
        "destinationConfig": {
            "project": "TestProject",
            "buildConfig": "TestBuildConfig"
        }
    }
}

Assistant

Responses are generated using AI and may contain mistakes.