Skip to main content

Runtime configurations

Deprecation notice

Runtime configurations are deprecated and may be removed in the future. Use Providers to manage infrastructure configuration and Dimensions to tag scopes with environment attributes.

Runtime configurations allowed platform teams to provision reusable environments that developers could assign to scopes, decoupling infrastructure provisioning from application operations.

How it worked​

  1. Define dimensions — Create attributes like environment and country with values like production, US. See Dimensions.
  2. Create runtime configurations — Combine dimension values with infrastructure settings (cloud account, region, etc.) stored via the NRN API.
  3. Assign to scopes — Developers selected a runtime configuration when creating a scope, inheriting the underlying infrastructure settings.
POST /runtime_configuration
{
  "nrn": "organization=1",
  "dimensions": {
    "environment": "development"
  },
  "values": {
    "some": "thing"
  }
}
POST /scope/1/runtime_configuration
{
  "id": 1234
}

Migration path​

Use Providers to define infrastructure configuration with inheritance across the organizational hierarchy, and Dimensions to tag scopes with semantic attributes.