Case Wylie cmwylie19

Run a local zot registry

docker run --platform linux/amd64 -d -p 3333:5000 --name oras-quickstart ghcr.io/project-zot/zot-linux-amd64:latest

Build Pepr image and library

npm run build:image

nmap -p 22 192.168.6.0/24 192.168.5.0/24

# Just the IPs
nmap -p 22 --open 192.168.6.0/24 192.168.5.0/24

# Use -T4 to speed it up (aggressive timing):
nmap -p 22 --open -T4 192.168.6.0/24 192.168.5.0/24

# Or output to a grep-friendly file:

git merge upstream/main --allow-unrelated-histories -X theirs

PEPR_OVERRIDE_IMAGE="pepr:dev" uds run test:uds-core-e2e --set FLAVOR=upstream --no-progress

export AWS_ACCESS_KEY_ID=""
export AWS_SECRET_ACCESS_KEY=""
export AWS_SESSION_TOKEN=""

aws configure 
aws eks update-kubeconfig --region <AWS_REGION> --name <EKS_CLUSTER_NAME>

docker pull docker.io/library/node:22-bookworm
docker inspect --format='{{index .RepoDigests 0}}' docker.io/library/node:22-bookworm

# or 
skopeo inspect docker://docker.io/library/node:22-bookworm | jq -r '.Digest'

gh workflow run container-scan.yaml --ref 1375

on:
  workflow_dispatch:

Kubernetes Watch

Kubernetes Watch reports changes on the resource defined by the URL and is configured through the query string.

It is the mechanism that backs Pepr Watch and Reconcile.
It is how Kubernetes Controllers and Informers track changes to resources
It can return several content-types like JSON, YAML, protobuf, CBOR and probably more

URL Construction

Keybase proof

I hereby claim:

I am cmwylie19 on github.
I am cmwylie19 (https://keybase.io/cmwylie19) on keybase.
I have a public key ASDGJ04T0MCyz9rzIMD6FmYjHh9Nc3vE_QFDgoKfXAXwjAo

To claim this, I am signing this object:

	const fs = require('fs');

	function reorganizeChangelog(filePath) {
	const changelog = fs.readFileSync(filePath, 'utf8');
	const lines = changelog.split('\n');

	const whatsChangedIdx = lines.findIndex(line => line.trim() === '## What\'s Changed');
	if (whatsChangedIdx === -1) {
	console.error('No "## What\'s Changed" section found.');
	return;