Docs

DevOps Config

What this screen is for

DevOps Config holds the per-tier defaults that environments inherit: what a new environment starts with, how pipelines are configured, how deployments behave, the gateway, the available actions, and database console access.

There is one page per tier. Dev, staging and production each have their own configuration, and changing one does not affect the others.

Before you start

To do this You need
Read the configuration env-by-branch.<env>.devops-config.read
Change it env-by-branch.devops-config.update
Create an entry env-by-branch.devops-config.create
Delete one env-by-branch.devops-config.delete

Flat names expand across tiers

env-by-branch.devops-config.read is a flat name. The backend checks it as env-by-branch.dev.devops-config.read, then staging, then production, then the flat name itself. Holding any one tier variant satisfies a flat-named route for that tier — so grant the tier you actually mean rather than relying on the flat name.

Opening it

Each tier has its own URL:

  • /ebb/dev/devops-config
  • /ebb/staging/devops-config
  • /ebb/production/devops-config

From the UI: open the tier’s environments page and use the environment settings icon in the header.

The interface

📸 Screenshot Placeholder: The DevOps Config page for the dev tier. Mark: (1) the environment-type selector showing Development / Staging / Production, (2) the cluster selector, (3) the six tabs.

# Control What it does When you’d use it
1 Environment type Development · Staging · Production Confirming which tier you are editing
2 Cluster selector The cluster this configuration applies to Always — configuration is per cluster
3 Tabs Six areas, below Depends on the job
Tab What it configures
Defaults What a newly created environment in this tier starts with
Pipelines Pipeline configuration and the pipeline source
Deployment How deployments behave in this tier
Gateway Ingress and routing
Actions Which actions are offered on an environment’s Operate › Actions tab
Database Console Database console access for this tier

Walkthroughs

Change what new environments start with

Requires env-by-branch.<env>.devops-config.update.

  1. Open the tier’s DevOps Config page.
  2. Select the cluster.
  3. On Defaults, adjust the settings.
  4. Save.

This applies to environments created afterwards. Existing environments keep what they were created with.

Configure SonarQube project mappings

  1. Open the DevOps Config page for the tier the environment runs on — the Quality tab’s own link takes you there.
  2. Select the cluster.
  3. On the relevant tab, add the project mappings.
  4. Return to the environment’s Test › Quality tab; metrics now resolve.

Change which actions are available

  1. Open the tier’s DevOps Config page, select the cluster.
  2. On Actions, adjust the list.
  3. Check an environment’s Operate › Actions tab to confirm.

Scenario

“No SonarQube project mappings configured for this application.”

This is the exact message the Quality tab renders. The link it offers takes you to the right tier’s configuration; the trap is which tier and cluster you then edit.

  1. Note which tier and cluster the environment belongs to. Configuration is per tier and per cluster, so getting either wrong means editing something real that has no effect on what you are looking at.
  2. Follow the link in the message, or go to /ebb/dev/devops-config directly, substituting staging or production as appropriate.
  3. Select the same cluster the environment runs on.
  4. Add the SonarQube project mapping.
  5. Save, then reopen the environment’s Test › Quality tab.
  6. If metrics are still absent, re-check step 1: an application in staging will not pick up a mapping added to the dev configuration, and nothing in the UI points this out.

When it doesn’t work

Symptom Cause How to check Fix
Changes had no effect on an existing environment Defaults apply to environments created afterwards The environment’s creation date Recreate it, or change it directly
Configuration saved but nothing changed Wrong tier, or wrong cluster The environment-type and cluster selectors Re-apply on the correct tier and cluster
Page is read-only You hold .read but not .update Access Explorer Ask for update on that tier
Granting the flat permission did not work as expected Flat names expand per environment The platform permission model Grant the specific tier variant

Next