Skip to main content
The Add Adobe Commerce Cloud Project wizard is how you onboard a new Magento Cloud project into DryRunPro. It is a five-step screen at: 
/v2/apps/dryrunpro/add-adobe-commerce-cloud-project
You reach it from the Add project button on the Projects tab, or from Settings, Adobe Commerce Cloud in the left rail. This page walks through every step in the wizard, the required Adobe-side permissions, what DryRunPro is doing under the hood, and what to do if any step fails.

​
What the wizard does

The wizard’s purpose is to grant DryRunPro super-admin access to the Adobe Commerce Cloud project so it can clone databases, pull media, build dryruns, and run code audits. That is non-trivial because Adobe Commerce Cloud requires explicit permission to give a third-party deploy bot the rights it needs. The five steps walk you through that permission grant, then ask you to paste the Cloud Project ID so DryRunPro knows which project to operate on.

​
Before you begin

You need:
  1. Super-admin access on the Adobe Commerce Cloud project, on the Adobe side. If you cannot add a user to the project on accounts.magento.cloud/user, you cannot complete this wizard. Ask the Adobe-side account holder to grant you super-admin first.
  2. The deploy-bot email address that DryRunPro is configured with for your tenancy. This is typically docker@247commerce.co.uk for the canonical DryRunPro deployment, but agency tenancies can configure their own. Ask your DryRunPro account manager if you do not know yours.
  3. The Cloud Project ID, a short alphanumeric handle from the URL of your project on account.magento.com/cloud/project/subscriptions/. Have it copied to the clipboard before you start the wizard.
  4. Admin or Team Leader role in DryRunPro, with the adobe_commerce_create permission. See Roles and Permissions.

​
The five steps

The wizard renders five purple step tiles across the top with a numbered title and a short instruction. Below the tiles, a screenshot animation cycles through the relevant Adobe Commerce Cloud screens for the active step, with left and right chevron arrows to advance. A blue Add Project button sits in the top-right of step 5. The Add Project button is the wizard’s submit. Until you reach step 5, the button is greyed out.

​
Step 1, list your Adobe Commerce Cloud projects

Click https://accounts.magento.cloud/user to view all projects in the Cloud. Then click the project title to add the user.
Open the Adobe Cloud accounts page in a new tab. Sign in with your Adobe ID. You will see a list of every Adobe Commerce Cloud project your Adobe ID has access to. Click into the project you want to onboard into DryRunPro. The screenshot in step 1 shows the Magento Cloud project picker with a project tile selected.

​
Step 2, open the setting wheel

Click the setting wheel icon on top to see configuration screen.
Inside the project, look for the small gear icon in the top navigation strip (next to the project name). Click it. The configuration drawer opens with tabs for Users, Domains, Certificates, Deploy Key, and Variables. The screenshot in step 2 highlights the gear icon with a red pointer.

​
Step 3, click Add User

Click Add User button to add dryrunpro user as super admin.
In the configuration drawer, click the Users tab. A table of existing users appears with an Add User button in the bottom-left. Click it. A new row appears for you to type the deploy-bot email address. The screenshot in step 3 shows the Users tab with the Add User button highlighted.

​
Step 4, tick SUPER USER

Click the SUPER USER checkbox to grant Super admin access. Add the deploy bot account (e.g. docker@247commerce.co.uk) whose SSH key and API token DRP uses.
Type the deploy-bot email into the Account email field. Tick the SUPER USER checkbox to elevate the user to super-admin (this is the permission level DryRunPro needs to clone databases and modify environments). Save the user. Adobe will email the deploy-bot mailbox a confirmation request. The mailbox is monitored automatically by DryRunPro and the confirmation is accepted within seconds, so you do not need to do anything else on the Adobe side. The screenshot in step 4 shows the user-creation dialog with the SUPER USER checkbox ticked.

​
Step 5, paste the project ID

Get the project ID from https://account.magento.com/cloud/project/subscriptions/ and add it on the next screen to add Project.
Open account.magento.com/cloud/project/subscriptions/ in a new tab. Find the project you just modified. Copy the Cloud Project ID (a short alphanumeric handle). Return to the DryRunPro wizard and click Add Project in the top right. The DryRunPro wizard now opens an input form: the Cloud project ID field, an Assign to team dropdown, and a Check access & Save button. Paste the Cloud Project ID, optionally pick a team from the dropdown, and click Check access & Save. DryRunPro will:
  1. Use its Cloud CLI credentials and the deploy-bot SSH key to attempt a connection to the Cloud Project ID you pasted.
  2. Read the project’s environment list, user list, and storage allocation.
  3. Generate a thirteen-character DryRunPro Project ID.
  4. Create the project card on the Projects tab.
If the connection succeeds, you are redirected to the Project Overview page for the new project.

​
Validation outcomes

The Check access & Save click can produce three outcomes. Success. DryRunPro reads the project, the deploy bot is super-admin, and the credentials work. The card appears in the Projects grid. Move on to spinning up your first dryrun. Deploy bot not authorised. Adobe rejects the connection because the deploy-bot user has not finished the email confirmation, or the SUPER USER checkbox was not ticked. The wizard shows the error and stays on the input form. Re-check step 4 in the Adobe console, then click Check access & Save again. Wrong project ID. Adobe returns “project not found” or “permission denied”. Most often this means you pasted a project ID for a different project than the one where you added the deploy bot. Double-check the project ID matches the one you modified in steps 1 to 4.

​
What DryRunPro does after a successful add

Once the project is added:
  1. DryRunPro snapshots the Adobe-side environment list and user list.
  2. The project card on the Projects tab populates with Adobe Commerce Cloud counters (Environments, Storage, Users) and DryRun Pro counters (Staging, Packages, Users, all initially zero).
  3. The team you picked in the dropdown is assigned. If you did not pick one, the card shows “No team” and you can assign it later.
  4. You can immediately use Create your own to spin up your first dryrun against any of the project’s environments.

​
Re-validating an existing project

If a project later loses its connection (someone removes the deploy bot from the Adobe side, or rotates the SSH key), the project card on the Projects tab will show a Connect with DryRun Pro modal instead of stats. The modal is the same input form as step 5: paste the Cloud Project ID, click Check access & Save, and the connection re-establishes. You do not need to re-run steps 1 to 4 unless the deploy bot was actually removed from the project’s user list.

​
Frequently asked questions

Can I add the same Cloud project ID twice? No. DryRunPro deduplicates by Cloud Project ID. If the project is already on your tenancy, the card appears in the Projects grid; if it is on a different tenancy, you cannot import it (each Cloud project belongs to one DryRunPro tenancy at a time). What email address should I add as the deploy bot? The default for the canonical DryRunPro deployment is docker@247commerce.co.uk. Agency tenancies that operate their own deploy-bot mailbox use that email instead. If you do not know which one to use, ask your DryRunPro account manager. Why does Adobe require the deploy bot to be SUPER USER? DryRunPro needs to read the database, mount the media volume, and modify environment variables to spin up a dryrun. Adobe Commerce Cloud only grants those rights at the SUPER USER tier. Lower tiers (admin, viewer) are not sufficient. The deploy bot did not auto-confirm the Adobe email. What now? Wait two minutes for the polling cycle. If the badge still shows “Pending” on the Adobe side after that, contact your DryRunPro account manager so they can manually trigger the confirmation handler. Can I add a project without specifying a team? Yes. Pick “No team” in the dropdown. You can assign a team later from the Project Overview page or from the dropdown on the project card. Where is the deploy bot’s SSH key stored? In the DryRunPro tenancy’s encrypted secrets store, keyed as DRP_ssh2id_rsa. It is rotated by your DryRunPro account manager on a fixed schedule and you do not need to interact with it directly. I cannot find the gear icon in step 2. Some Adobe Commerce Cloud project layouts hide the gear icon behind the project’s Configure project tab. If you do not see a gear, click into the project name, then look for “Configure” in the right-hand panel. The Users tab is in the same place either way. What happens to running dryruns if I revoke the deploy bot’s super-admin access on the Adobe side? Currently running dryruns keep working until they hit their next build cycle. The next build attempt will fail because DryRunPro can no longer authenticate. Re-grant super-admin access (or run the wizard again) to restore.