open-index/open-npm huggingface dataset:
npm package: @fmenesesg/backstage-plugin-quay
Description: Welcome to the quay-frontend plugin! This plugin will show you information about your docker images within quay
Latest version: 0.1.8

# quay-frontend

Welcome to the quay-frontend plugin!
This plugin will show you information about your docker images within quay

_This plugin was created through the Backstage CLI_

## Getting started

### Enabling frontend

1. Install the plugin

   ```bash
   yarn workspace app add @fmenesesg/backstage-plugin-quay
   ```

2. Set the proxy to desired Quay server

   ```yaml
   # app-config.yaml
   proxy:
     '/quay/api':
       target: 'https://quay.io'
       changeOrigin: true
   ```

3. Enable additional tab on the entity view page

   ```ts
   // packages/app/src/components/catalog/EntityPage.tsx
   import { QuayPage, isQuayAvailable } from '@fmenesesg/backstage-plugin-quay';

   const serviceEntityPage = (
     <EntityPageLayout>
       // ...
       <EntityLayout.Route if={isQuayAvailable} path="/quay" title="Quay">
         <QuayPage />
       </EntityLayout.Route>
     </EntityPageLayout>
   );
   ```

4. Annotate your entity with

   ```yaml
   metadata:
     annotations:
       'quay.io/repository-slug': `<ORGANIZATION>/<REPOSITORY>',
   ```
npm package: @fmenesesg/threescale-backstage-provider
Description: This is a plugin for synchronizing 3scale content into [Backstage.io](https://backstage.io/) catalog.
Author: Francisco Meneses
Latest version: 0.0.9

# 3scale Backstage provider

This is a plugin for synchronizing 3scale content into [Backstage.io](https://backstage.io/) catalog.

## Install

1. Install the plugin

   ```sh
   yarn add --cwd packages/backend @fmenesesg/threescale-backstage-provider
   ```

## Configure

3scale Backstage provider allows configuration of one or many providers using the `app-config.yaml` configuration file of Backstage. Use a `threeScaleApiEntity` marker to start configuring them.

```yaml
# app-config.yaml

catalog:
  providers:
    threeScaleApiEntity:
      dev:
        baseUrl: https://<TENANT>-admin.3scale.net
        accessToken: <ACCESS_TOKEN>
        schedule: # optional; same options as in TaskScheduleDefinition
          # supports cron, ISO duration, "human duration" as used in code
          frequency: { minutes: 1 }
          # supports ISO duration, "human duration" as used in code
          timeout: { minutes: 1 }
```

Once you've done that, you'll also need to add the segment below to `packages/backend/src/plugins/catalog.ts`:

```ts
/* packages/backend/src/plugins/catalog.ts */

import { ThreeScaleApiEntityProvider } from '@fmenesesg/threescale-backstage-provider';

[...]
  const builder = await CatalogBuilder.create(env);

  /** ... other processors and/or providers ... */
  builder.addEntityProvider(
    ThreeScaleApiEntityProvider.fromConfig(env.config, {
      logger: env.logger,
      scheduler: env.scheduler
    }),
  );

  const { processingEngine, router } = await builder.build();
[...]
``` 

## Troubleshoot

After having started your Backstage app, you should see some lines like those below in logs:

```log
[1] 2023-02-13T15:26:09.356Z catalog info Discovered ApiEntity API type=plugin target=ThreeScaleApiEntityProvider:dev
[1] 2023-02-13T15:26:09.423Z catalog info Discovered ApiEntity Red Hat Event (DEV, v1.2.0) type=plugin target=ThreeScaleApiEntityProvider:dev
[1] 2023-02-13T15:26:09.620Z catalog info Discovered ApiEntity Red Hat Event (TEST, v1.1.0) type=plugin target=ThreeScaleApiEntityProvider:dev
[1] 2023-02-13T15:26:09.819Z catalog info Discovered ApiEntity Red Hat Event (PROD, v1.1.0) type=plugin target=ThreeScaleApiEntityProvider:dev
[1] 2023-02-13T15:26:09.819Z catalog info Applying the mutation with 3 entities type=plugin target=ThreeScaleApiEntityProvider:dev
```