[Backstage]: v0 sandboxes

[davixcky]

Objectives

• Create boilerplate and setup basic api calls
• Create card to list sandboxes
• Allow to select columns
• Allow to filter by cluster name
• Show labels
• Fix usage that don't require to import main route. If route is not added in App.tsx the cards are not working.
• Show sandbox detail
• Overview card

Deploy

• Deploy under @signadot-lib scope
• Release v0 version
• Add to announcements page (dashboard) #4
• Include release notes

Out of the scope

• Allow to filter by label
• [ ]

[foxish]

We want to deploy under @signadot-lib scope right? Before we release Also we need to make this repo OSS first? What about backstage plugin submission steps?

[foxish]

For example, there is https://backstage.io/docs/plugins/add-to-directory/#submission-tips that we would need to follow. And then to create https://backstage.io/docs/plugins#suggesting-a-plugin. I think they need us to create an issue in the backstage repo sooner than later.

[davixcky]

Moved the backstage further details in #3

[davixcky]

@foxish i don't think we need to put our plugin in the comunnity plugins. I think only catalog would be sufficient, then we have to depend on their workflows to change our plugin and so on

[foxish]

Okay, that's fine, but IIUC we still need to open an issue on the community repo for a new plugin (in order to list in their catalog) even if we're not putting the code there. Can you check how other folks do this and how long it might take to get approved?