Label connections by environment

Every connection has an Environment field. Pick Development, Staging or Production from the suggestions, or type any name, such as heartie-pro or eu-staging. The label is shown on the connection card and next to the connection name in the query header, so you always see which environment a tab points at.

The label is informational. It does not change permissions or add confirmation prompts: queries are read-only on every connection regardless of the label, and Infra writes always require a reviewed plan.

Set or change the label

Open New connection, or Edit connection for an existing one (the settings icon on its card in Connections).
In Environment, choose a suggestion or type a custom name.
Click Save connection.

New connections default to Development.

How labels appear

Connections page: a badge in the top-right corner of each card.
Query header: a badge next to the connection name, for example Commerce database · Production.

Labels in Infra

Kubernetes and K3s connections are listed under Infra → 集群资源 (cluster resources). There, the 环境 (environment) selector above the connection list filters them by this label: 全部环境 shows all of them, and connections with an empty label appear under 未分组 (ungrouped). When no cluster connection matches the selected environment, DevOpsPad tells you to switch environments or add a K3s or Kubernetes connection.

Infra project environments are defined separately in the local project mapping; each environment there points at a connection by name. See project.yaml and the Infra overview.

Naming tips

Keep labels consistent across your team’s machines if you share an Infra project through Git. The connection names referenced by the project must match; credentials can differ per person.
Use one label per real environment rather than per server.
Put the environment in the connection name too if you open many tabs at once: tab titles show the resource, not the label.