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

pps-register-permissions-gh-action

v0.0.16

Published

A GitHub action that reads a payload from your repo to register your application permissions with PPS

Downloads

1

Readme

PPS Register Permissions GitHub action

This action reads the permissions.json file in your repository and registers the permissions and groups contained within that file with PPS.

Inputs

Files

permissions.json

Required The file that contains your application permissions - this file should be in the top level of your repository.

{
    "permissions": [
      {
        "name": "View Permission",
        "description": "Permission that grants user access to view nodes",
        "applicationInternalCode": "ViewPermission"
      },
      {
        "name": "Create Permission",
        "description": "Permission that grants user access to create nodes",
        "applicationInternalCode": "CreatePermission"
      }
    ],
    "groups": [
      {
        "name": "Basic Access Group",
        "description": "This group provides the permissions required for basic access to our application",
        "applicationInternalCode": "BasicAccessGroup",
        "permissionInternalCodes": [
          "ViewPermission",
          "CreatePermission"
        ]
      }
    ]
  }

example permissions.json

Environment Variables

These environment variables must be set in your repository secrets under the actions section: Settings > Secrets > Actions > New Repository Secret

CLIENT_ID

Required The client ID of your application.

CLIENT_SECRET

Required The client secret for your application.

ENVIRONMENT

Required The environment variable determines which PPS environment you wish to register your permissions with.

Accepted Values: development, staging, production

Example usage

name: 'Register Application Permissions'
on:
  push:
    branches:
      - main # Replace with your main branch name

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - id: s1
        uses: actions/checkout@v2
      - id: s2
        uses: sainsburys-tech/[email protected]
        with:
          CLIENT_ID: ${{ secrets.CLIENT_ID }}
          CLIENT_SECRET: ${{secrets.CLIENT_SECRET}}
          ENVIRONMENT: "development"