Skip to content

Environment groups — overview

Group environments with user-defined tags to keep the Stack Harbor PaaS dashboard manageable when you operate more than a handful of them.

Environment groups are user-defined tags you attach to environments to filter and organise them in the dashboard. They are the answer to “I have twenty environments and I need to find the staging cluster for project X without scrolling.”

A group is a tag. An environment can carry several tags. Tags can be nested into subgroups for finer cuts. Once tagged, environments are filterable from the group panel and from a dedicated column in the environment list.

What groups give you

  • A clear cross-cut over your environment landscape — by project, by stage, by stack, by region, by any axis you find useful.
  • Nested groups for sharper filters — for example, a top-level project-x group with dev, staging, prod subgroups.
  • Multi-tagging — an environment can belong to several groups at once, so an environment can be tagged as project-x and prod and eu-central simultaneously.
  • A persistent filtered view — once you click into a group, the rest of the dashboard scopes itself to that group until you exit.

Where groups live in the dashboard

The main entry point is the Env Groups menu, above the environment list. From there you can:

  • See every group on your account.
  • Open a group to apply its filter.
  • Open the Manage view to see the full group tree and edit, nest, or remove groups.
  • Sort by region or by sharing state from the same panel.

When a group is selected, it appears as a breadcrumb element on the Env Groups panel and the environment list narrows to its members. Click Env Groups itself to clear the filter and return to the full list.

Naming and structure

There are no hard rules. Use letters, numbers, spaces, and special characters. Group names exist only inside your account. A typical scheme is one of:

  • By lifecycle stage — development, testing, staging, production.
  • By project or client — project-x, client-acme, internal-tools.
  • By technology — java, node, postgres-heavy.
  • By region — when you span more than one region and want a quick filter.

Groups are independent of the actual environment configuration. Re-tagging an environment changes nothing about how it runs.

What this section covers

See also