Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Configure multiple SDK keys

2 minute read

Initialize and run multiple SDK instances in one application, each bound to a different SDK key and environment. For an explanation of when and why to use this approach, refer to Understanding multiple SDK keys.

Before you begin, ensure the following:

  • SDK v6.x or later for your platform.

  • One SDK key per application-environment you plan to use.

  • The flags you plan to evaluate exist in each application and environment being queried.

  • Network access to CloudBees Unify endpoints from your runtime.

Set up multiple SDK keys

The following steps are SDK-agnostic. For language-specific code examples, refer to the SDK references listed in the related pages section.

  1. Retrieve the SDK keys for the environments you plan to use.

  2. Initialize a separate SDK instance for each key.

  3. Decide how to route requests to instances, for example by tenant, region, or environment selector.

  4. Perform register, fetch, and stream setup on each instance as required by your SDK.

  5. Evaluate flags using the selected instance, passing a consistent user or context object for accurate targeting.

  6. Tag logs or metrics for each instance, and shut down instances you no longer need.

Apply these practices to maintain clear isolation between instances, consistent evaluations, and reliable operations.

Instance management

Store instance references for reuse. Use consistent naming conventions for SDK keys.

Flag naming

Use prefixes to distinguish flags from different configurations. For example: prod_enableFeature vs staging_enableFeature.

Custom properties

Set custom properties on the specific instance. Avoid using static custom property methods with multiple SDK keys.

Error handling

Set up configuration fetched handlers for each instance. Monitor for network errors per instance.

Troubleshoot

Use the following to diagnose and resolve common issues with multiple SDK keys.

Wrong environment evaluated

Ensure you select the intended SDK instance before evaluation.

No updates applied

Confirm that register, fetch, or streaming is configured for that specific instance.

Callbacks not firing

Attach listeners to the same instance that performs fetch or streaming.

Unexpected differences

Compare flag definitions, targeting rules, and salts across environments.

High network activity

Reduce the number of active instances or adjust polling or stream settings.

Install server-side SDKs
Mobile SDK reference