This tutorial will guide you through the steps required to set Roadie up for basic use within your organization. Once completed, you will:
- Be an admin user of Roadie.
- Have connected Roadie to your organization’s GitHub account.
There are 3 kinds of Backstage resource used in this tutorial.
Userentity represents an employee at your company.
Groupentity represents a team or larger organizational structure.
Componententity represents a piece of software like a website or backend service.
In order to complete this guide, you will need the following things:
- Access to a Roadie account. If you do not yet have access, please join the waiting list.
- A GitHub Cloud or GitHub Enterprise Cloud account.
- A test service on GitHub which you can make changes to.
Roadie needs to connect to GitHub in order to function. This can be setup by installing the Roadie GitHub App. Installing the GitHub App will allow Roadie to:
- Access the YAML metadata files that Backstage needs to operate.
- Read your GitHub organisation’s users and team structure into backstage.
- Make requests from the browser on your behalf e.g. listing open pull requests.
You can find a link to install the GitHub app in the Backstage application:
- Click the Administration link in the bottom left
- Click the Settings tab along the top of the Administration page and then the Integrations link
- Click on the link to install the GitHub app.
- Follow the steps to install the App
- You may need to wait up to 2 minutes for the GitHub integration to become active
ℹ️ If you are not an owner of your GitHub organization, you will need to ask an owner to approve the App installation and then contact us to enable the App.
Roadie admins have special powers such as the ability to add and remove Backstage plugins. We will use GitHub teams to create an admin group for Roadie.
ℹ️ Admin groups are not a security measure. They hide certain UX features from regular users in order to simplify the experience. Backstage does not currently support role based access control (RBAC).
Visit GitHub Teams in your organization’s GitHub account and click the New Team button.
Set the Team name to
roadie-backstage-admin. This is a special value and must be an exact match.
Enter a Description such as “Users with Backstage administration abilities.”.
Leave Parent team unselected and click the Create team button.
By default, GitHub adds your account to the team as a member. You are now an admin on Roadie and should have access to two main features:
- Access to the Secrets panel via the “Administration” link in the sidebar.
- The ability to add and remove plugin cards and tabs (see red-circled icons).
ℹ️ It can take some time for Roadie to refresh the list of teams from GitHub teams. If you do not see admin functions immediately, please wait a few minutes and try again.
The GitHub permissions that Roadie needs are all read only. You can also choose to allow access to all repos, or select the repos that you would like to give permission to.
Here is a description of each of the permissions requested:
- Actions (read) - enables the Backstage plugin that renders Github workflow actions on the component page.
- Code (read) - backstage makes use of a yaml config file, generally kept in the root directory of a GitHub project. Backstage needs read access to the code so that it can read the backstage catalog config file.
- Members (read) - This allows Backstage to authenticate users of your Github org and ensure only users of your organisation can access it. It also allows for ownership to be assigned and displayed for each service.
- Metadata (read) - This gives Roadie read only access to various pieces of metadata about the GitHub organisation used only in order to enable functionality.
- Organisation administration (read) - Enables the API to show Roadie the interaction limits for a user.
- Security events (read) - This allows Backstage to render a security insights plugin on the component page.
Let’s add a component to Backstage.