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

@janus-idp/backstage-scaffolder-backend-module-quay

v1.7.1

Published

The quay-actions module for @backstage/plugin-scaffolder-backend

Downloads

1,943

Readme

Quay actions for Backstage

This module provides Backstage template actions for Quay.

The following actions are currently supported in this module:

  • Create a Quay repository

Installation

Run the following command to install the action package in your Backstage project

yarn workspace backend add @janus-idp/backstage-scaffolder-backend-module-quay

Installing the action on the legacy backend

  1. Register the Quay actions by modifying the packages/backend/src/plugins/scaffolder.ts file from your project with the following changes:

    import { CatalogClient } from '@backstage/catalog-client';
    import { ScmIntegrations } from '@backstage/integration';
    import {
      createBuiltinActions,
      createRouter,
    } from '@backstage/plugin-scaffolder-backend';
    
    import { Router } from 'express';
    
    import { createQuayRepositoryAction } from '@janus-idp/backstage-scaffolder-backend-module-quay';
    
    import type { PluginEnvironment } from '../types';
    
    export default async function createPlugin(
      env: PluginEnvironment,
    ): Promise<Router> {
      const catalogClient = new CatalogClient({
        discoveryApi: env.discovery,
      });
    
      const integrations = ScmIntegrations.fromConfig(env.config);
    
      const builtInActions = createBuiltinActions({
        integrations,
        catalogClient,
        config: env.config,
        reader: env.reader,
      });
    
      const actions = [...builtInActions, createQuayRepositoryAction()];
    
      return await createRouter({
        actions,
        logger: env.logger,
        config: env.config,
        database: env.database,
        reader: env.reader,
        catalogClient,
        identity: env.identity,
      });
    }
  2. Optional: If you are doing the previous step for the first time, you also have to install the @backstage/integration package

    yarn workspace backend add @backstage/integration

Installing the action on the new backend

Add the following to your packages/backend/src/index.ts file:

const backend = createBackend();

// Add the following line
backend.add(
  import('@janus-idp/backstage-scaffolder-backend-module-quay/alpha'),
);

backend.start();

Configuration

Add the Quay actions to your templates, see the example file in this repository for complete usage examples

action: quay:create-repository
id: create-quay-repo
name: Create quay repo
input:
  baseUrl: https://quay.io
  token: UW1dLVdCTj8uZWNuIW97K1k0XiBkSmppVU9MYzFT
  name: foo
  visibility: public
  description: This is a foo repository
  namespace: bar
  repoKind: image

Usage

Action: quay:create-repository

Input

| Parameter Name | Type | Required | Description | Example | | -------------- | :----: | :------: | --------------------------------------------------------------------------------- | ---------------------------------------- | | name | string | Yes | Quay repository name | foo | | visibility | string | Yes | Visibility setting for the created repository, either public or private | public | | description | string | Yes | Description for the created repository | This if foo repository | | token | string | Yes | Authentication token, see docs | UW1dLVdCTj8uZWNuIW97K1k0XiBkSmppVU9MYzFT | | baseUrl | string | No | Base url of a quay instance, defaults to https://quay.io | https://foo.quay.io | | namespace | string | No | Namespace to create repository in, defaults to the namespace the token belongs to | bar | | repoKind | string | No | Created repository kind, either image or application, if empty defaults to image | image |

Output

| Name | Type | Description | | ------------- | :----: | ------------------------------------------ | | repositoryUrl | string | Quay repository URL created by this action |