Adobe Commerce Cloud Project and Environment Management

Transcript

Hi, this is Russell with Adobe Commerce. Today’s session is about project and environment management for Adobe Commerce Cloud. Some prerequisites would be that you’ve already been invited to an Adobe Commerce Cloud project with your email address and then that same email address is associated to your Mage ID. Here’s an example of what that looks like.

Let’s start by going to console.adobecommerce.com so we can log in. If you’re brand new to Adobe Commerce Cloud and you’ve recently created your account, you should have a Mage ID. Once again, here’s what it looks like. If you complete your login process, but you land on a page that says something like create your first project, that’s a good indicator that you’ve either used the wrong email address or perhaps you’ve chosen the wrong IMS organization. Another opportunity is that your Mage ID along with your email address is incorrect. This will likely require a support ticket for you to resolve, really not the topic of this tutorial, so let’s keep things moving along and show you a more typical login experience.

So now that we’ve logged in, you can see that I have several projects assigned. You can use this search at the top of the page to limit those projects being shown.

Let’s continue and we’re going to go to the top right and we’re going to choose my profile. This section has a few different options starting with your profile image. You can adjust your first and last name. You can set your country. Next is authentication settings and this is where you would enable or disable MFA. Another section is API tokens and the last one is the SSH key. You do need a public SSH key saved and connected to your Adobe Commerce Cloud environment using SSH. Here’s a demonstration. If it’s been a little while since you’ve used SSH on a cloud environment, when you try to log in, you’re going to be denied. You can use the CLI command magento cloud login and then when you click yes authorize, when you try again, you get connected to your environment. So now you can see what it looks like for a typical experience. To add a new key to your profile, all you need to do is click add new, give it some and then copy in your computer’s public key. One important note is once you save the key, these cloud environments need to be redeployed for you to be able to use that SSH key to SSH in. A new Adobe Commerce Cloud project often resembles this structure. There’s master and then there’s production, staging, and integration. This particular one has two integration environments but it’s also common to see two or more staging environments. It’s also nice to know that you can rename these. Once you log in, if you choose a project at this point but you haven’t chosen an environment, several buttons are disabled, for example SSH and logs. However, when you click on the master branch, you can see the URL for this project and you can also see the SSH credentials and then also how to view the container logs.

The last one that I want to talk about is just to the right of container logs. It’s here, you can just use the traditional git clone. Depending on your permission level, you might see a gear icon. Currently, we’re viewing the master environment, so this gear icon takes you to the master environment settings. Anything saved here will override what is set at a project level. You can read more on this part of the cloud UI and how it’s managed and some of the options in the official Adobe Commerce docs found in Experience League. Another interesting thing to note is some of these changes on these environments will trigger a redeployment. And that’s the reason for this spinning icon. It’s an indicator that the environment has triggered a deployment and it needs to be completed before those settings are used. You can see the same icon on the activity page along with a short description for what triggered the deployment. The other area under settings is variables. And this is useful for environment specific settings. For example, every environment can have a unique admin URL and you can define that here. Another useful security setting is your composer credentials. These sensitive composer values will not be part of your code and they’re only available here for people who have access to your Commerce Cloud projects.

Up next, we’ll talk a little bit about access control. Being invited through this channel, this access control, means that the invitee will be able to go to console.adobecommerce.com to view the project and then also whatever environments that you’ve configured. They’ll also have SSH access to those specified environments.

I’d also like to highlight the fact that if you choose this option for project admin, this provides the highest level of access to all of your cloud environments. This should be used with extreme caution and not used often. It’s better off that you invite people to individual projects and environments with correct permission levels. It’s also a good idea that you should audit this list perhaps monthly or so in order to ensure that old users are removed as soon as possible.

Invitations like these should be restricted to those specific environments with different access levels. There’s a few that you can choose from, so be sure to read more up on this topic, heading over to ExperienceLink to fully understand the power for this functionality and ensure that you provide the right level of permission to each person so they can accomplish their tasks.

And lastly, if you forget to redeploy the environment after creating the new user, they’ll be denied when they try to log in. After you invite someone, they’ll receive an email, and they must follow the instructions. They’re not automatically added. And you can see the status of the invitation here. And if you click on one, you can get some additional information as well as a few options. You can resend the invitation or revoke it.

And that’s what I’ll do here as a demonstration. We’re going to click Revoke, and then we’re going to click Accept. One final thing that should be mentioned is that an Adobe Commerce Cloud invitation is different than the user created to manage the Adobe Commerce Store and access the Commerce Back Office. To access the Adobe Commerce Back Office, that is completely independent and not affiliated with the Adobe Commerce Cloud project users that we just went through. Because of this, you can have users that only have access to the Commerce Back Office but Each type of invite is independent, and you’re able to provide as much flexibility and granularity as possible to meet your unique requirements.

Well, this is the end for this tutorial on the Commerce Cloud Environment project-level UI. Please come back to Experience League to learn more about Adobe Commerce as well as all of the other Adobe products.