Skip to main content
The Project Overview page is the live snapshot of one Adobe Commerce Cloud project inside DryRunPro. You reach it by clicking View Details on a project card on the Projects tab, and it opens at: 
/v2/apps/dryrunpro/projectoverview?project_id=<DryRunPro Project ID>
This page documents the four header stats, the Project Details panel, the Adobe Cloud Environments list, the Project Credentials block, the DRP Composer Overrides surface, and the four tabbed sub-views at the bottom of the page (Staging Environments, Staging Packages, Cloud Users, Snapshots).

​
What you see at the top

The page header is the project name in large bold text, e.g. “Project name: Bahrain Duty Free Company WLL (Dublin)”. Directly below the name sits a single red Delete Project button that triggers the Delete Project workflow. Underneath that, three counter cards stretch across the page:
  1. Environments (large green number, e.g. 5). This is the count of Adobe-side environments DryRunPro can see. It includes integration, master, pr-1068, production, and staging on the example project. Below the number, a small More info link expands the Adobe Cloud Environments list further down.
  2. Storage (e.g. “N/A”). Adobe Commerce Cloud does not always surface a storage figure via the Cloud CLI; when missing, DryRunPro reports N/A rather than guessing. Below it, a More info link.
  3. Users (e.g. 13). The Adobe-side user count, pulled from the Cloud CLI. Below it, a More info link that scrolls to the Cloud Users tab.

​
Project Details panel

A two-column block underneath the counters:
  • Description: the human-readable description set during the Add Project wizard.
  • Status: the current DryRunPro lifecycle status, e.g. “code: provisioned” once the deploy bot has been validated and the Cloud CLI handshake succeeds.
  • Current Plan: the Adobe Commerce Cloud plan tier (Starter, Pro, etc.). DryRunPro reads this from the Cloud CLI.
  • Assigned Team: a dropdown showing the currently assigned team (e.g. “No team”, “Cakebox”, “Blitz”, “BDFC”). Pick a different team and click Assign Team to commit.
  • View More Details: a blue link that expands a hidden section with deeper Adobe-side metadata (account ID, region, plan SKU, billing reference). The detail varies by what Adobe exposes for the project.

​
Adobe Cloud Environments

This list shows every Adobe-side environment DryRunPro can see for the project, one per line. A typical Adobe Commerce Cloud project surfaces:
  • integration (the shared development line)
  • master (the deployment trunk)
  • pr-1068 (an active feature branch)
  • production (the live store)
  • staging (the Adobe-side staging tier)
Each name is a link that, where applicable, opens that environment’s URL or the Cloud Manager view for that environment. The list is read-only on this page; to spin up a DryRunPro dryrun against any of these environments, jump to the Dryrun Environments tab and use Create your own.

​
Project credentials (staging clone)

A single password-style input labelled Project credentials (staging clone), captioned “Required to clone this project (db dump, media, assets). Get them from accounts.magento.cloud + API Tokens.” Paste the API token DryRunPro should use to clone this project’s database, media, and asset payloads when it spins up a dryrun. The Save button on the right encrypts and stores the token. DryRunPro never persists the token in plaintext, and the input always shows the masked “Saved. Enter new value to replace.” once a token is in place.

​
DRP Composer overrides

The DRP Composer overrides block contains a textarea where you can paste project-level Composer override rules that DryRunPro injects when it builds a dryrun’s Composer manifest. Use this when you need to:
  • Force a specific Magento extension version that differs from the production composer.lock.
  • Substitute a vendor package while a fix is being verified.
  • Pin a Magento core patch ahead of an Adobe release.
Paste the override snippet, click Save, and the next dryrun build will pick it up. To revert, click Clear all DRP overrides to wipe the override set and fall back to the project’s canonical composer.json. A small caption underneath reads: “Project level overrides used by DRP in Step 2. Remove entries on failback or Cloud original push. No DRP overrides saved.”

​
The four tabbed sub-views

A tab bar at the bottom of the page exposes four lists:

​
Staging Environments

A table of every dryrun environment currently running for this project. Columns:
  • Project Environments (the Adobe-side branch the dryrun was spun from, e.g. “staging”)
  • Product ID (the DryRunPro short ID, e.g. “47k74xtjq6jya”)
  • Assigned to (the user who owns the dryrun, e.g. “DryrunPro admin”)
  • DryRun Url (a clickable link, e.g. https://staging-47k74xtjq6jya-2.dryrunpro.com)
  • Status (e.g. “Active”)
  • Date Created
  • Action (View / Edit / Delete buttons)
Click a row’s View action to land on the Staging Detail page for that dryrun.

​
Staging Packages

A table of completed staging packages produced by past dryruns. Cross-references the Docker packages tab. Columns include the Staging ID, Cloud Project, Branch, Docker Snapshot link, Warden Package link, and Updated timestamp.

​
Cloud Users

A table of every user with access to the Adobe Commerce Cloud project on the Adobe side, pulled from the Cloud CLI. Columns:
  • Email Address
  • Name
  • Project role (admin or viewer)
  • Cloud ID (the Adobe-side opaque user ID)
  • Add to Dryrunpro (the action button, see below)
  • Action (View / Edit / Delete, only visible for users who have already been added to DryRunPro)
The Add to Dryrunpro column is the join point between the Adobe-side roster and the DryRunPro roster. Click Add next to a Cloud user and DryRunPro will provision them as a Project User on the DryRunPro side, sending a magic-link invite to their email. Once added, the row shows a green “Added” badge and the View / Edit / Delete actions appear. This is how a Magento agency onboards an enterprise customer’s in-house team. The customer’s engineers are already users on the Adobe Commerce Cloud project, so the agency does not need to retype their emails. One click on Add per row and the DryRunPro side mirrors the Adobe side.

​
Snapshots

A table where you spin up on-demand snapshots of the dryrun environment for archival or debug. Columns:
  • Project Environments dropdown (which environment to snapshot, default “Staging”)
  • Snapshot type radio buttons: Codebase, Media, Database
  • Assigned to dropdown (which user to attribute the snapshot to)
  • Status
  • Date Created
  • Action (a green Snapshot button that triggers the run)
Snapshots are a read-only deliverable. They do not change the dryrun’s state; they capture a frozen copy at the moment the button is clicked. Useful for “I want to roll back this dryrun to where it was yesterday” or “I want to ship a copy of the database to Adobe support”.

​
When you would visit this page

  • After spinning up a dryrun from the Create your own launcher, you land here to confirm the environment is healthy.
  • When a dryrun fails to build, you come here to read the Project credentials, DRP overrides, and Adobe Cloud Environments list to diagnose what went wrong.
  • When onboarding a new engineer, you visit Cloud Users and click Add per row.
  • When you need to clear DRP overrides ahead of a production push.
  • When a customer asks “what is the URL of our current dryrun?”, you check Staging Environments for the live URL.

​
Frequently asked questions

Why is my Storage value “N/A”? Adobe Commerce Cloud does not always expose a numeric storage figure through the Cloud CLI. DryRunPro reports N/A rather than fabricate a value. Functional behaviour is unaffected. What is the difference between a snapshot and a Docker package? A Docker package is the compressed container set produced when a dryrun completes its build, intended for laptop-side debugging and reproducibility. A snapshot is an on-demand frozen copy of the dryrun’s codebase, media, or database, intended for archival or for handing off to Adobe support. Both are downloadable artefacts, but they capture different layers of the stack. Can I add a Cloud user who is not on the Adobe side yet? Not from this tab. The Cloud Users table is the Adobe-side roster, mirrored read-only. To add a user who only needs DryRunPro access (no Adobe-side access), use the Project Users screen. What happens if I clear all DRP overrides? The next dryrun build for this project will fall back to the canonical composer.json. Any patches you were testing via overrides will be skipped. Existing running dryruns keep the override set they were built with. Can I share the DryRun URL externally? Yes. Each dryrun URL is publicly resolvable through the configured CDN (Fastly or Cloudflare, see CDN settings). It is not gated by DryRunPro authentication. If you need it gated, set the dryrun’s CDN mode to “DRP behaviour” and add an access password on the Staging Detail page. How do I find the URL parameter project_id for a project? It is shown in the URL of this page. Copy it from the address bar. You can also find it on the project card on the Projects tab as the small grey “Project ID:” line.