Content Hub's Default Environment Specific Settings
The ability to mark a setting as environment specific is one of Content Hub's great features. These particular settings are omitted when creating an export package, meaning they won't be deployed to the environment the package is imported into.
Environment Specific by Default
The following settings are marked as environment specific by default:
| Category | Name | System Owned? | Identifier |
|---|---|---|---|
| Dam Settings | FetchSetting | ✔ | M.Setting.FetchSetting |
| DamSettings | PublicCollectionConfiguration | ✔ | M.Setting.PublicCollectionConfiguration |
| DistributionSettings | Configuration | ✔ | M.Setting.Configuration |
| ChiliConfiguration | FontsConfiguration | ❌ | M.Setting.FontsConfiguration |
| ChiliConfiguration | ChiliConfiguration | ❌ | M.Setting.ChiliConfiguration |
| ChiliConfiguration | ChiliStudioConfiguration | ✔ | M.Setting.ChiliStudioConfiguration |
| PortalConfiguration | Authentication | ❌ | M.Setting.Authentication |
| PortalConfiguration | AssetExtensionDataConfigurationSetting | ✔ | M.Setting.AssetExtensionDataConfigurationSetting |
| PortalConfiguration | CORSConfiguration | ❌ | M.Setting.CORSConfiguration |
Although system owned settings are not visible in the UI, and cannot be edited - I've included them here for completeness.
These settings, therefore, cannot be propagated between environments using an import/export package. Any changes made to these settings will need to me performed separately on each environment (unless you're using the Content Hub CLI Serialisation - but that's a topic for another day!).
Summary
Content Hub's environment specific settings are a powerful feature that allows you to manage different configurations for different environments. By understanding which settings are environment specific by default, you can ensure any changes to them are propagated correctly.