Service Catalog Import about backstage-showcase HOT 3 OPEN

As discussed, there is currently a problem with authorization. If GitHub integration is configured using Github App, the authorized user should be able to import only repositories to which the user has permission. There is currently no auth system that provides this level of permissions.

We are going to break this down into multiple stages.

Stage 1

• janus-idp/software-templates#148

This will be similar to the Backstage catalog-import plugin but done using Software Template.
Using the template will give users the ability to customize the import flow to fit their needs.

Stage 2
once the RBAC is ready we will extend the template with some kind of repository selector. This will allow us to do an actual bulk import.

Stage 3
extending the flow with the ability to automatically generate catalog-info.yaml based on the information detected from the git repository.

from backstage-showcase.

I'm tracking this ticket, since I'm certain it will be important to a number of development teams that I work with. Most already have anywhere from a small handful to dozens of apps running in their k8s clusters, so having a way to import those into the Backstage catalog will be an important feature for any team that isn't starting with a green field.

from backstage-showcase.

You can already import an existing app in the catalog. Not only a green field app.
If done via the source code repo, the existing apps will appear in the Kubernetes plugin (and Topology plugin). Then we can provide more features to move from one CI tool to another, or migrate workloads to another platform, etc.

from backstage-showcase.