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

@socialgouv/sre-seal

v1.14.5

Published

`yarn global add @socialgouv/sre-seal` and you'll get `sre-seal` command available.

Downloads

54

Readme

@socialgouv/sre-seal

yarn global add @socialgouv/sre-seal and you'll get sre-seal command available.

:warning: Need kubeseal CLI installed on your system.

CLI

Usage: sre-seal [options] <KEY=someSecretMessage>

Options:
  --namespace  k8s namespace (optional in dev)                   [default: null]
  --name       k8s secret name (optional in dev)   [default: "some-secret-name"]
  --context    k8s context                                     [default: "dev"]
  --from       path to existing seal file
Examples
# Dev secrets
# crypt a bunch of key/values
cat values.yml | sre-seal > sealed.yml
# crypt a single value
echo "PASSWORD=pouet" | sre-seal > sealed.yml

# Prod secrets have mandatories namespace and secret name
cat values.yml | sre-seal --context prod --namespace project --name secret-name > sealed.yml

# Add new secret to some existing secret file with `--from`
echo "PASSWORD=pouet" | sre-seal --from current-seal.yml > sealed.yml

JavaScript

const YAML = require("yaml");
const { cryptFromSecrets } = require("@socialgouv/sre-seal");

cryptFromSecrets({
  name: "some-secret-name",
  //namespace: "cdtn-admin",
  context: "dev", // or prod with namespace
  secrets: {
    PGRST_JWT_SECRET: "FyH2ETW8zulPobZ9j6wr3jWM5OtsK2zR84NLBIb0",
    KIKOO: "Bjd9ddeR84NLBIb0",
  },
})
  .then((sealed) => console.log(YAML.stringify(sealed)))
  .catch(console.log);

:bulb: Copy values from Rancher secret view from Chrome console : copy(Array.from(document.querySelectorAll("table tbody tr")).map(node => [node.querySelector("td:nth-child(1)").innerText, node.querySelector("td:nth-child(3)").innerText]).reduce((a, c) => ({...a, [c[0]]:c[1]}),{}))