Compare Environments on ZopDay: Every Difference Highlighted
A new Compare environments button on the project page shows how the same services differ between environments. Stage and prod, or environments from different projects, appear with every difference highlighted. Missing services are marked Missing. Copy to environment writes the baseline settings to the other environments.
Pick the Projects, Environments and Services to Compare
Step 1 is to pick the projects, environments and services to compare. The first environment is the baseline. Environments from different projects can be selected in the same comparison.
| What you pick | Detail |
|---|---|
| Projects | One or more projects |
| Environments | Two or more, the first is the baseline |
| Services | All or a subset of the services in those environments |
The baseline environment is the reference point. Every other environment is compared against it. You can also pick any services from any project to compare.
If a service has a different name in another environment, you can pair the two by hand. Pairing lets the comparison match services that are the same but named differently across environments.
Teams that manage environment-level overviews can check resource usage before running a comparison.
One Column per Environment With Every Difference Highlighted
Step 2 shows one column per environment. Each service shows its version, and differences are highlighted. Missing services are marked Missing.
Open a service to compare its overview, revisions, environment variables, network, databases and settings. Each tab shows how many differences it has. Observability shows one environment at a time.
| Tab | What it compares |
|---|---|
| Overview | Service overview across environments |
| Revisions | Revision history across environments |
| Environment variables | Variable names and values across environments |
| Network | Network configuration across environments |
| Databases | Database settings across environments |
| Settings | Service settings across environments |
Each tab shows the number of differences it has. A service that exists in one environment but not in another is marked Missing in the missing column.
Teams using role-based access controls can control who compares environments and who copies settings.
Copy to Environment Writes the Baseline Settings
Copy to environment copies environment variables, the port and health-check settings from the baseline to the other environments. It shows exactly what will change before anything is written. Secret values are never shown, compared or copied.
| What Copy to environment copies | Detail |
|---|---|
| Environment variables | From baseline to the other environments |
| Port | From baseline to the other environments |
| Health-check settings | From baseline to the other environments |
The preview shows exactly what will change. Nothing is written until the preview is confirmed. Secret values are never shown, compared or copied across any part of the comparison.
Teams that manage developer seats at the organisation level can use Copy to environment to align settings across environments.
