deploy: Helper manifests for testing in-flight branches

deploy/1-image-stream.yaml

@@ -0,0 +1,5 @@
+apiVersion: image.openshift.io/v1
+kind: ImageStream
+metadata:
+  name: graph-data
+  namespace: openshift-update-service

deploy/2-build-config.yaml

@@ -0,0 +1,19 @@
+apiVersion: build.openshift.io/v1
+kind: BuildConfig
+metadata:
+  name: graph-data
+  namespace: openshift-update-service
+spec:
+  source:
+    type: Git
+    git:
+      uri: https://github.com/openshift/cincinnati-graph-data.git
+      ref: master
+  strategy:
+    type: Docker
+  output:
+    to:
+      kind: ImageStreamTag
+      name: graph-data:latest
+  triggers:
+  - type: ConfigChange

deploy/3-update-service.yaml

@@ -0,0 +1,10 @@
+apiVersion: updateservice.operator.openshift.io/v1
+kind: UpdateService
+metadata:
+  name: example
+  namespace: openshift-update-service
+spec:
+  graphDataImage: >-
+    image-registry.openshift-image-registry.svc:5000/openshift-update-service/graph-data:latest
+  releases: quay.io/openshift-release-dev/ocp-release
+  replicas: 1

deploy/README.md

@@ -0,0 +1,9 @@
+# Test deployments
+
+For conveniently testing graph-data state against a locally installed [OpenShift Update Service][osus] operator, edit `spec.source.git` in [`2-build-config.yaml`](2-build-config.yaml) to point at your fork, and then:
+
+```console
+$ oc apply -f .
+```
+
+[osus]: https://catalog.redhat.com/software/operators/detail/5f0f35842991b4207fcdb202