---
sidebar_label: Legacy runtime configurations
doc_id: 02fb5aac-5ced-494f-97e1-7b6f0c4a89f8
description: >-
  Legacy feature for creating reusable environments across scopes. Deprecated
  in favor of Providers.
keywords:
  - runtime configurations
  - environments
  - scopes
  - legacy
---

# Runtime configurations

:::warning Deprecation notice

Runtime configurations are deprecated and may be removed in the future. Use [**Providers**](../providers/overview.md) to manage infrastructure configuration and [**Dimensions**](./dimensions.md) 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](./dimensions.md).
2. **Create runtime configurations** — Combine dimension values with infrastructure settings (cloud account, region, etc.) stored via the [NRN API](../providers/nrn-api.md).
3. **Assign to scopes** — Developers selected a runtime configuration when creating a scope, inheriting the underlying infrastructure settings.

```http
POST /runtime_configuration
{
  "nrn": "organization=1",
  "dimensions": {
    "environment": "development"
  },
  "values": {
    "some": "thing"
  }
}
```

```http
POST /scope/1/runtime_configuration
{
  "id": 1234
}
```

## Migration path

Use [Providers](../providers/overview.md) to define infrastructure configuration with inheritance across the organizational hierarchy, and [Dimensions](./dimensions.md) to tag scopes with semantic attributes.