projectriff / dev-utils Goto Github PK

CloudEvents defines an encoding for JSON. The subscribe command is emitting events in JSON, but is not following the spec.

https://github.com/cloudevents/spec/blob/v1.0/json-format.md#3-envelope

...we don't have any

In addition to payload, contentType and headers, add cloud-events fields like id, source, type and specversion and time.

Usage text says this:

Usage:
  publish <stream-name> <payload> [flags]

The payload actually is its own flag so it should be

Usage:
  publish <stream-name> [flags]

The example looks ok

Running kubectl delete pod dev-utils only returns after about 30s and the pod appears to be waiting for something to terminate. From kubectl pod describe:

Normal  Killing    14s   kubelet, docker-desktop  Stopping container dev-utils

Looking at the running processes in the container i see the following (not sure if that's related)

4 S root         1     0  0  80   0 -  1156 -      13:23 ?        00:00:00 sh -c tail -f /dev/null
0 S root         7     1  0  80   0 -  1141 -      13:23 ?        00:00:00 tail -f /dev/null

This happens even when there no other publish or subscribe processes running.

Watching subscribed streams from 2 terminal sessions with dev-utils kubectl exec appears to fail after subscribing to a 2nd stream.

The ERROR: EOF appears in the first subscriber, when a 2nd one is added from a 2nd terminal session.

Dependabot couldn't parse the go.mod found at /go.mod.

The error Dependabot encountered was:

go: github.com/spf13/[email protected] requires
	github.com/spf13/[email protected] requires
	github.com/grpc-ecosystem/[email protected] requires
	gopkg.in/[email protected]: invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /opt/go/gopath/pkg/mod/cache/vcs/748bced43cf7672b862fbc52430e98581510f4f2c34fb30c0064b7102a68ae2c: exit status 128:
	fatal: The remote end hung up unexpectedly

View the update logs.

Add kafkacat to dev-utils to allow users to tail kafka topics

The steps in https://github.com/projectriff-demo/demo#run-dev-utils-pod appear easier, and more generic (not dependent on runtime choice)

Currently, subscribe and publish can run only in the k8s cluster. Add ability and instructions on running them locally.

Sometimes when inside the pod it's useful to have access to the riff cli. Access to the cluster will be restricted to the rbac policies applied to the pod's service account.

Requires projectriff/cli#198

Instructions use --image=projectriff/dev-utils but that pulls in an older image, looks like CI doesn't push a "latest" tag

Dependabot couldn't parse the go.mod found at /go.mod.

The error Dependabot encountered was:

go: github.com/spf13/[email protected] requires
	github.com/spf13/[email protected] requires
	github.com/grpc-ecosystem/[email protected] requires
	gopkg.in/[email protected]: invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /opt/go/gopath/pkg/mod/cache/vcs/748bced43cf7672b862fbc52430e98581510f4f2c34fb30c0064b7102a68ae2c: exit status 128:
	fatal: The remote end hung up unexpectedly

View the update logs.

Sometimes when inside the pod it's useful to have access to kubectl. Access to the cluster will be restricted to the rbac policies applied to the pod's service account.

The publish and subscribe were implemented based on a draft of RFC 0003. Now that the RFC is approved, the command args and behavior should implement the behavior defined by the RFC.

There is no way to exit the subscribe command cleanly. Since the command will run until it encounters an error, the only way to gracefully exit is via SIGTERM, but that doesn't exit cleanly.

This is particularly important for scripts that fail when a command exits abnormally, like FATS.