📂 Apply fork specific files

.deviate.yaml

@@ -0,0 +1,5 @@
+upstream: https://github.com/knative-sandbox/kn-plugin-event.git
+tags:
+  synchronize: true
+resyncReleases:
+  enabled: true

.github/workflows/golangci-lint.yaml

@@ -0,0 +1,11 @@
+name: Code Style
+
+on:
+  pull_request:
+    branches: [ 'main', 'release-*' ]
+
+jobs:
+
+  style:
+    uses: knative/actions/.github/workflows/style.yaml@main
+

Makefile

@@ -0,0 +1,37 @@
+mkfile_path := $(abspath $(lastword $(MAKEFILE_LIST)))
+current_dir := $(dir $(mkfile_path))
+
+CI ?= false
+PROW_JOB_ID ?= 0
+PROW = $(shell [ "$(CI)" = "true" ] && [ "$(PROW_JOB_ID)" != "0" ] && echo "true" || echo "false")
+
+ifeq ($(PROW),true)
+	# Openshift CI runs as high UID user
+	export HOME = /tmp
+	export GOPATH = /tmp/go
+	# Reset the goflags to avoid the -mod=vendor flag
+	export GOFLAGS =
+endif
+
+build:
+	./mage build
+.PHONY: build
+
+unit:
+	./mage test
+.PHONY: unit
+
+test: unit
+.PHONY: test
+
+e2e:
+	openshift/e2e-tests.sh
+.PHONY: e2e
+
+dockerfiles:
+	go run github.com/openshift-knative/hack/cmd/generate@latest \
+		--root-dir "$(current_dir)" \
+		--generators dockerfile \
+		--app-file-fmt "/usr/bin/%s" \
+		--dockerfile-image-builder-fmt "registry.ci.openshift.org/openshift/release:rhel-8-release-golang-%s-openshift-4.17"
+.PHONY: dockerfiles

OWNERS

@@ -1,9 +1,17 @@
+# The OWNERS file is used by prow to automatically merge approved PRs.
+
 approvers:
-- technical-oversight-committee
-- knative-release-leads
-- client-writers
-- kn-plugin-event-approvers
+- rhuss
+- dsimansk
+- mgencur
+- cardil
+- openshift-cherrypick-robot
 
 reviewers:
-- client-writers
-- kn-plugin-event-approvers
+- rhuss
+- dsimansk
+- mgencur
+- cardil
+- jrangelramos
+- lkingland
+- matejvasek

README.md

@@ -1,184 +1,28 @@
 # kn-plugin-event
 
-[![Mage](https://github.com/knative-extensions/kn-plugin-event/actions/workflows/go.yml/badge.svg?branch=main)](https://github.com/knative-extensions/kn-plugin-event/actions/workflows/go.yml)
-[![Go Report Card](https://goreportcard.com/badge/knative-extensions/kn-plugin-event)](https://goreportcard.com/report/knative-extensions/kn-plugin-event)
-[![Releases](https://img.shields.io/github/release-pre/knative-extensions/kn-plugin-event.svg?sort=semver)](https://github.com/knative-extensions/kn-plugin-event/releases)
-[![LICENSE](https://img.shields.io/github/license/knative-extensions/kn-plugin-event.svg)](https://github.com/knative-extensions/kn-plugin-event/blob/main/LICENSE)
-[![Maturity level](https://img.shields.io/badge/Maturity%20level-ALPHA-red)](https://github.com/knative/community/tree/main/mechanics/MATURITY-LEVELS.md)
+This repository holds OpenShift's fork of 
+[`knative-sandbox/kn-plugin-event`](https://github.com/knative-sandbox/kn-plugin-event) 
+with additions and fixes needed only for the OpenShift side of things.
 
-`kn-plugin-event` is a plugin of Knative Client, for managing cloud events from
-command line.
+[![Mage](https://github.com/cardil/kn-plugin-event-fork/actions/workflows/go.yml/badge.svg?branch=release-next)](https://github.com/cardil/kn-plugin-event-fork/actions/workflows/go.yml)
+[![GolangCI-Lint](https://github.com/cardil/kn-plugin-event-fork/actions/workflows/golangci-lint.yaml/badge.svg?branch=release-next)](https://github.com/cardil/kn-plugin-event-fork/actions/workflows/golangci-lint.yaml)
 
-## Description
+## How this repository works ?
 
-With this plugin, you can build and send the cloud events to publicly available
-addresses (URLs) or to Addressable (Kubernetes service, Knative service, broker,
-channels, etc) inside of Kubernetes cluster.
+The `main` branch holds up-to-date specific [openshift files](./openshift)
+that are necessary for CI setups and maintaining it. This includes:
 
-## Usage
+- Scripts to create a new release branch from `upstream`
+- CI setup files & tests scripts
 
-### Build an event
+Each release branch holds the upstream code for that release and our
+OpenShift's specific files.
 
-You could use `build` subcommand to create an event with a help of convenient
-builder-like interface. It may be helpful to send that even later or use it in
-other context.
+## CI Setup
 
-#### Simplest event
+For the CI setup, two repositories are of importance:
 
-```sh
-$ kn event build -o yaml
-data: {}
-datacontenttype: application/json
-id: 81a402a2-9c29-4c27-b8ed-246a253c9e58
-source: kn-event/v0.4.0
-specversion: "1.0"
-time: "2021-10-15T10:42:57.713226203Z"
-type: dev.knative.cli.plugin.event.generic
-```
-
-#### More complex example
-
-```sh
-$ kn event build \
-    --field operation.type=local-wire-transfer \
-    --field operation.amount=2345.40 \
-    --field operation.from=87656231 \
-    --field operation.to=2344121 \
-    --field automated=true \
-    --field signature='FGzCPLvYWdEgsdpb3qXkaVp7Da0=' \
-    --type org.example.bank.bar \
-    --id $(head -c 10 < /dev/urandom | base64 -w 0) \
-    --output json
-{
-  "specversion": "1.0",
-  "id": "RjtL8UH66X+UJg==",
-  "source": "kn-event/v0.4.0",
-  "type": "org.example.bank.bar",
-  "datacontenttype": "application/json",
-  "time": "2021-10-15T10:43:23.113187943Z",
-  "data": {
-    "automated": true,
-    "operation": {
-      "amount": "2345.40",
-      "from": 87656231,
-      "to": 2344121,
-      "type": "local-wire-transfer"
-    },
-    "signature": "FGzCPLvYWdEgsdpb3qXkaVp7Da0="
-  }
-}
-```
-
-### Send an event
-
-To send an event, you should use the `send` subcommand. The `send` command uses
-the same builder-like interface as the `build` command. You can send an event to
-the public address of your application or to a supported in-cluster resource by
-using the `--to` option.
-
-#### Sending to a public address
-
-To send an event to a public address, you should pass the address to the `--to`
-option:
-
-```sh
-$ kn event send \
-    --field player.id=6354aa60-ddb1-452e-8c13-24893667de20 \
-    --field player.game=2345 \
-    --field points=456 \
-    --type org.example.gaming.foo \
-    --to http://ce-api.foo.example.org/
-```
-
-> **NOTE**: All arguments, except `--to` are optional. Use
-> `kn event send --help` to see full usage information.
-
-#### Sending to the in-cluster resources
-
-Sending events to the in-cluster resources is done with a companion *Job*
-that is deployed on your cluster. This allows `kn-event` to send your events to
-resources that are not publicly accessible.
-
-Send an event to a Knative service `showcase` in current namespace:
-
-```sh
-$ kn event send \
-    --type org.example.kn.ping \
-    --id $(uuidgen) \
-    --field event.data=98765 \
-    --to showcase
-```
-
-To send the event to the broker named `foo` in `my-ns` namespace:
-
-```sh
-$ kn event send --to broker:foo:my-ns
-```
-
-> **NOTE**: The `--to` option follows [the Kn sink format](https://github.com/knative/client/blob/main/docs/cmd/kn_trigger_create.md#options).
-> Use `kn event send --help` to see full format description.
-
-## Install
-
-You can download a pre-built version of `kn-plugin-event` from
-[our release page](https://github.com/knative-extensions/kn-plugin-event/releases)
-. Choose the one that fits your platform.
-
-When the download is ready, you should be ready to use `kn-plugin-event` as a
-standalone binary. Check the available commands with:
-
-```sh
-kn-event-<OS>-<ARCH> --help
-```
-
-### Install to work with `kn` CLI
-
-If you'd like to use the plugin with `kn` CLI, install the plugin by simply
-copying the executable file under `kn` plugins directory as:
-
-```sh
-$ mkdir -p ~/.config/kn/plugins
-$ cp build/_output/bin/kn-event-<OS>-<ARCH> \
-    ~/.config/kn/plugins/kn-event
-```
-
-Check if plugin is loaded
-
-```sh
-$ kn -h
-```
-
-Run it
-
-```sh
-$ kn event -h
-```
-
-## Building
-
-If you'd like to build the plugin yourself, you will need to have
-[Golang](https://golang.org/) installed on your machine. Check the `go.mod` file
-for current minimum version.
-
-To build the plugin, just invoke the following script:
-
-```sh
-$ ./mage
-```
-
-Project will check, test and build binaries for various platforms. You'll get an
-executable plugin binary named `kn-event-<OS>-<ARCH>` in `build/_output/bin`
-dir.
-
-You could list all available build targets with:
-
-```sh
-$ ./mage -l
-```
-
-### Updating dependencies
-
-To update dependencies, please utilize the standard `hack/update-deps.sh`
-script. It's also needed to run this script if you are doing any changes to Go
-libraries. Read more about it at [knative/hack](https://github.com/knative/hack)
-repository.
+- This repository
+- [openshift/release](https://github.com/openshift/release) which
+  contains the configuration of CI jobs that are run on this
+  repository