Skip to content
Documentation | Universal Foundry

Self-Managed Horde Stream Configurations

First-time Setup

Section titled “First-time Setup”

Self-managed Horde stream configurations are disabled by default. To enable them please reach out to support@universalfoundry.io.

Universal Foundry support will walk you through the initial setup steps.

Configuring Self-Managed Horde Stream Configuration JSONs

Section titled “Configuring Self-Managed Horde Stream Configuration JSONs”

In the setting page, scroll down to the “Perforce Based Stream Configuration JSONs” section.

Create a new Perforce stream which will be used to store the new Horde stream JSONs. Enter the path to that stream in “Configs Stream Name” and commit the exact streams that have been provided by Universal Foundry. Once the migration is complete, you will be free to modify these.

The “Stream Configuration JSONs” section of the settings page has been prepopulated with your current configuration. Leave these untouched until builds are running smoothly.

Once everything is set up, email support to have Horde switched over to use the Perforce-based streams.

Requirements for Self-Managed Horde Stream Configurations

Section titled “Requirements for Self-Managed Horde Stream Configurations”
  • The name of each stream configuration JSON file must be unique.
  • The stream configuration JSON file should already exist in the Perforce stream.
  • The Perforce stream referenced by the stream configuration JSON should already exist and have the correct permissions for Horde to access the stream.
  • Never change the name key of a stream configuration JSON file. Instead create a new stream.

Available Macros

Section titled “Available Macros”

DefaultPerforceCluster: The value that should always be used as the clusterName.

UBAConfig: Universal Foundry baseline UBA configuration. This should always be included as UfCompileArguments even if your organization doesn’t use remote UBA agents.

CookArgs: Universal Foundry baseline cook configuration. This can be included as UfExtraCookArguments if using Universal Foundry quickstart.

Horde Stream Configuration JSON

Section titled “Horde Stream Configuration JSON”

Epic’s documentation for the stream configuration can be found here.

However there are some keys managed by Universal Foundry that should never be included in your self-managed stream configurations.

These are:

  • acl
  • notificationChannel
  • workspaceTypes
  • agentTypes

If you need to make changes to these keys please reach out to support@universalfoundry.io.

Configuration Change Notifications

Section titled “Configuration Change Notifications”

If you’re organization has Slack enabled in Universal Foundry then the person who makes a change to a stream configuration JSON will receive a direct message when that stream configuration has been applied by Horde.