Working with projects and workspaces

Transcript

In this tutorial, we will be showing the Adobe Developer Console workflow, which is needed to allow you to interact with API Mesh. And we will also be creating our first API Mesh using Adobe Commerce as the source and interact with it. This workflow combines both UI and command line interactions. The first step is to get invited to an organization as a developer, where all developers in your org will interact and build projects. To get access, you can request an invite from your Adobe organization administrator. Once you have been invited, you will have specific access to certain parts within your organization and you will be able to navigate the Adobe Developer Console by going to this URL right here, developer.adobe.com and clicking on the Console button. In my case, I already accepted the developer invitation, but I had to create an account because it was my first time interacting with Adobe Developer Console. For those of you who have already had an account, you can just go ahead and accept the invitation and that action will just give you access to your new org and proceed with interacting with the projects, workflows and start building upon APIs, events and runtimes. You can also browse whatever other colleagues in your organization have already been creating and start collaborating upon that.

Let’s say you are part of multiple organizations and you want to create a brand new project and you have just been invited to another organization. To switch those organizations, you can switch on the top right corner, like so, and choose your organization. Once here, you can begin by creating a new project within your organization. To do this, we will create the project and choose from template. Please do choose template when doing this. Next, select App Builder and you get to name your project. The two fields that are required here is the project title and an app name. We’ll modify the project title, API Mesh Test, and we will also change the app name to API Mesh Test. No spaces here. As you can see here, it will create two workspaces by default and add the runtime necessary, but it will also add more spaces like development space. We’ll just create a dev space here so we can have dev stage in production as a normal workflow in any project and click save. In the case you get a conflict like this, it might be a naming conflict, so I suggest renaming the app name because it’s a unique name with something else. There we have it. We have created our first workspace. We have to add all these APIs to every one of them to actually access API Mesh. By default, no workspace will have API Mesh API added to it, so we must add it. You can click here on each one of the workspaces, add service, click on API, click on API Mesh, next. You get to actually put a domain here, click save, and you will get your generated credentials going back here. We can see a small icon here that pertains to the API mesh that was actually added. We must repeat this for all workspaces, and you can see after adding that workspaces have to contain the API icon, which means API Mesh was added to the workspace. Next, we are going to use the console. We’re going to use IO command by logging in first because if we run other commands from IO, we will not be able to do any operations. First we need to log in. This will actually open my login through a webpage, and since I’m already logged in, it will confirm that it authenticated correctly. Going back to my console, I should be able to see that I’m currently logged in into my default organization, but I have no project and no workspace selected. Therefore, next I have to select the project and a workspace and possibly even change the organization depending on which organization I interact with. When operating with works, projects, and workspaces, we will use the IO console command. IO console org list will actually list all organizations. In this case, I see that it’s seeing my previous organization, not the current one that I’m having here in this webpage. Even if I actually switch it from the web browser, that’s because IO command upon login will only use the organization that you will work on. To fix this, you must use the following scenario. IO logout.

Logging off from here and also from the web browser.

And when logging in, you must choose the right org at that time.

Going back to the console, I can see which organizations do I have access with and sure enough, it is the new organization.

Next, we can access the projects, we can do a quick comment to see all listed available projects.

This list should match exactly what we have here. Breaking all projects. This list of projects should match the one that I grabbed in the CLI.

Next, we can select the project. We will actually select API mesh test. Next, we will select the workspace.

I will choose for this the development workspace.

Now, we are ready to use API mesh command. In order to do that, we can list what plugins we will have available.

We also can see if API mesh is available.

And we can see here IO API mesh. This list all the commands that we can perform with API mesh. This concludes this video tutorial and you have learned how to organize your work in projects and workspaces and you are now ready to start creating some API meshes.