Update README links to point to community-plugins repository (#3931)

Signed-off-by: gaelgoth <gothuey.gael@gmail.com>
This commit is contained in:
Gaël G. 2025-05-09 21:47:31 +02:00 committed by GitHub
parent 3a82752a64
commit 6c0f6ee354
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
24 changed files with 72 additions and 15 deletions

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-azure-devops-backend': patch
---
Update README links to point to community-plugins repository.

View File

@ -53,5 +53,5 @@ Here's how to get the backend up and running:
## Links
- [Frontend part of the plugin](https://github.com/backstage/backstage/tree/master/plugins/azure-devops)
- [Frontend part of the plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/azure-devops/plugins/azure-devops)
- [The Backstage homepage](https://backstage.io)

View File

@ -0,0 +1,6 @@
---
'@backstage-community/plugin-azure-sites-backend': patch
'@backstage-community/plugin-azure-sites': patch
---
Update README links to point to community-plugins repository.

View File

@ -26,7 +26,7 @@ Configuration Details:
- `domain` can be found by visiting the [Directories + Subscriptions settings page](https://portal.azure.com/#settings/directory). Alternatively you can inspect the [Azure home](https://portal.azure.com/#home) URL - `https://portal.azure.com/#@<Your_Domain>/`.
- `tenantId` can be found by visiting [Azure Directory Overview page](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade).
- (Optional) `clientId` and `clientSecret` can be the same values you used for [Azure DevOps Backend](https://github.com/backstage/backstage/tree/master/plugins/azure-devops-backend) or [Azure Integration](https://backstage.io/docs/integrations/azure/org#app-registration) as long as this App Registration has permissions to read your function apps.
- (Optional) `clientId` and `clientSecret` can be the same values you used for [Azure DevOps Backend](https://github.com/backstage/community-plugins/tree/main/workspaces/azure-devops/plugins/azure-devops-backend) or [Azure Integration](https://backstage.io/docs/integrations/azure/org#app-registration) as long as this App Registration has permissions to read your function apps.
- (Optional) `allowedSubscriptions` is an array of `id` that will be used to iterate over and look for the specified functions' app. `id` can be found the [Subscriptions page](https://portal.azure.com/#view/Microsoft_Azure_Billing/SubscriptionsBlade).
### Integrating

View File

@ -16,7 +16,7 @@ The following sections will help you get the Azure plugin setup and running
### Azure Sites Backend
You need to set up the [Azure Sites Backend plugin](https://github.com/backstage/backstage/tree/master/plugins/azure-sites-backend) before you move forward with any of these steps if you haven't already.
You need to set up the [Azure Sites Backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/azure-sites/plugins/azure-sites-backend) before you move forward with any of these steps if you haven't already.
### Entity Annotation

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-badges-backend': patch
---
Update README links to point to community-plugins repository.

View File

@ -201,7 +201,7 @@ The badges backend api exposes two main endpoints for entity badges. The
- `/badges/entity/:namespace/:kind/:name/badge-specs` List all defined badges
for a particular entity, in json format. See
[BadgeSpec](https://github.com/backstage/backstage/tree/master/plugins/badges/src/api/types.ts)
[BadgeSpec](https://github.com/backstage/community-plugins/blob/main/workspaces/badges/plugins/badges/src/api/types.ts)
from the frontend plugin for a type declaration.
- `/badges/entity/:namespace/:kind/:name/badge/:badgeId` Get the entity badge as
@ -220,7 +220,7 @@ The badges backend api exposes two main endpoints for entity badges. The
- `/badge/entity/:entityUuid/badge-specs` List all defined badges for a
particular entity, in json format. See
[BadgeSpec](https://github.com/backstage/backstage/tree/master/plugins/badges/src/api/types.ts)
[BadgeSpec](https://github.com/backstage/community-plugins/blob/main/workspaces/badges/plugins/badges/src/api/types.ts)
from the frontend plugin for a type declaration.
### Custom badge styles

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-copilot-backend': patch
---
Update README links to point to community-plugins repository.

View File

@ -169,5 +169,5 @@ For more details on using the GitHub Copilot and Teams APIs, refer to the follow
## Links
- [GitHub Copilot Plugin Frontend](https://github.com/backstage/backstage/tree/master/plugins/copilot)
- [GitHub Copilot Plugin Frontend](https://github.com/backstage/community-plugins/tree/main/workspaces/copilot/plugins/copilot)
- [Backstage Homepage](https://backstage.io)

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-cost-insights-common': patch
---
Update README links to point to community-plugins repository.

View File

@ -4,5 +4,5 @@ Shared isomorphic code for the cost-insights plugin.
## Links
- [Frontend part of the plugin](https://github.com/backstage/backstage/tree/master/plugins/cost-insights)
- [Frontend part of the plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/cost-insights/plugins/cost-insights)
- [The Backstage homepage](https://backstage.io)

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-entity-feedback': patch
---
Update README links to point to community-plugins repository.

View File

@ -44,7 +44,7 @@ out of the box, this plugin will not work when you test it.
### Backend
You need to setup the [Entity Feedback backend plugin](https://github.com/backstage/backstage/tree/master/plugins/entity-feedback-backend) before you move forward with any of these steps if you haven't already
You need to setup the [Entity Feedback backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/entity-feedback/plugins/entity-feedback-backend) before you move forward with any of these steps if you haven't already
### Installation

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-explore': patch
---
Update README links to point to community-plugins repository.

View File

@ -11,7 +11,7 @@ The following sections will help you get the Explore plugin setup and running.
### Backend
You need to setup the
[Explore backend plugin](https://github.com/backstage/backstage/tree/master/plugins/explore-backend)
[Explore backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/explore/plugins/explore-backend)
before you move forward with any of these steps if you haven't already.
### Installation

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-linguist-backend': patch
---
Update README links to point to community-plugins repository.

View File

@ -130,5 +130,5 @@ linguist:
## Links
- [Frontend part of the plugin](https://github.com/backstage/backstage/tree/master/plugins/linguist)
- [Frontend part of the plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/linguist/plugins/linguist)
- [The Backstage homepage](https://backstage.io)

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-periskop': patch
---
Update README links to point to community-plugins repository.

View File

@ -13,7 +13,7 @@ Each of the entries in the table will direct you to the error details in your de
## Setup
1. Configure the [periskop backend plugin](https://github.com/backstage/backstage/tree/master/plugins/periskop-backend/)
1. Configure the [periskop backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/periskop/plugins/periskop-backend)
2. Install the plugin by running:

View File

@ -0,0 +1,5 @@
---
'@backstage-community/plugin-playlist': patch
---
Update README links to point to community-plugins repository.

View File

@ -10,7 +10,7 @@ The following sections will help you get the Playlist plugin setup and running
### Backend
You need to setup the [Playlist backend plugin](https://github.com/backstage/backstage/tree/master/plugins/playlist-backend) before you move forward with any of these steps if you haven't already
You need to setup the [Playlist backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/playlist/plugins/playlist-backend) before you move forward with any of these steps if you haven't already
### Installation

View File

@ -0,0 +1,6 @@
---
'@backstage-community/plugin-rollbar-backend': patch
'@backstage-community/plugin-rollbar': patch
---
Update README links to point to community-plugins repository.

View File

@ -93,5 +93,5 @@ access account token._
## Links
- [Frontend part of the plugin](https://github.com/backstage/backstage/tree/master/plugins/rollbar)
- [Frontend part of the plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/rollbar/plugins/rollbar)
- [The Backstage homepage](https://backstage.io)

View File

@ -4,7 +4,7 @@ Website: [https://rollbar.com/](https://rollbar.com/)
## Setup
1. Configure the [rollbar backend plugin](https://github.com/backstage/backstage/tree/master/plugins/rollbar-backend/README.md)
1. Configure the [rollbar backend plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/rollbar/plugins/rollbar-backend)
2. If you have standalone app (you didn't clone this repo), then do
@ -62,5 +62,5 @@ metadata:
## Links
- [Backend part of the plugin](https://github.com/backstage/backstage/tree/master/plugins/rollbar-backend)
- [Backend part of the plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/rollbar/plugins/rollbar-backend)
- [The Backstage homepage](https://backstage.io)