npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@croz/plugin-ibm-apic-backend

v1.0.2

Published

Welcome to the apic-public backend plugin!

Downloads

2

Readme

apic-public

Welcome to the apic-public backend plugin!

This plugin was created through the Backstage CLI

Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running yarn start in the root directory, and then navigating to /apic-public.

You can also serve the plugin in isolation by running yarn start in the plugin directory. This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads. It is only meant for local development, and the setup for it can be found inside the /dev directory.

Standalone run

For standalone run, the standalone router is exposed (located at src\service\standaloneRouter.ts) with a method for synchronization that you can access by navigating to /apic-public-standalone/syncApic.

Exposed method triggers sync with IBM API Connect to fetch all entities related to the defined provider. The configuration for the provider is provided as environment variables located inside .env file.

Installation instructions

Install the plugin into backstage:

cd packages/backend
yarn add @croz/plugin-ibm-apic-backend
yarn install

Add proxy config to the app-config.yaml file:

catalog:
  providers:
    ibmApic:
      default:
        baseUrl: ${IBM_APIC_API_URL}
        # provider/your-realm
        realm: ${IBM_APIC_REALM}
        clientId: ${IBM_APIC_CLIENT_ID}
        clientSecret: ${IBM_APIC_CLIENT_SECRET}
        username: ${IBM_APIC_SERVICE_ACCOUNT_USERNAME}
        password: ${IBM_APIC_SERVICE_ACCOUNT_PASSWORD}

Register plugin inside the catalog. The catalog is located at packages/backend/src/plugins/catalog.ts

...
import {APICEntityProcessor, APICEntityProvider} from "@croz/plugin-ibm-apic-backend";
...


...
    const builder = CatalogBuilder.create(env);
    builder.addProcessor(new ScaffolderEntitiesProcessor());
    
    const cacheService = env.cache.getClient();

    const apicEntityProviders = APICEntityProvider.fromConfig(env.config, {
        id: 'default',
        logger: env.logger,
        cache: cacheService,
        database: env.database,
        schedule: env.scheduler.createScheduledTaskRunner({
             frequency: {minutes: 30},
             timeout: {minutes: 1},
             initialDelay: {seconds: 15}
        }),
    });
    builder.addEntityProvider(
        apicEntityProviders,
    );
    
    const entityProcessor = new APICEntityProcessor(env.config, env.logger, cacheService)
    builder.addProcessor(entityProcessor)
...

Catalog is refreshed every 30 minutes.