AETHER-2196 Add onos-config developer note
Change-Id: I8db0a0ae644177943cc61df65d0c192ef7eeac4c
diff --git a/developer/roc.rst b/developer/roc.rst
index 07c9d3a..cfbb42d 100644
--- a/developer/roc.rst
+++ b/developer/roc.rst
@@ -233,6 +233,27 @@
kind load docker-image sdcore-adapter:my-tag
+Developing using a custom onos-config
+-------------------------------------
+
+The onos-operator is responsible for building model plugins at runtime. To do this, it needs source code
+for onos-config that matches the onos-config image that is deployed. One way to do this is to fork the
+onos-config repository and commit your onos-config changes to a personal repository, and then reference
+that personal repository in the values.yaml. For example::
+
+ onos-config:
+ plugin:
+ compiler:
+ target: "github.com/mygithubaccount/onos-config@mytag"
+ image:
+ repository: mydockeraccount/onos-config
+ tag: mytag
+ pullPolicy: Always
+
+In the above example, the operator will pull the image from `mydockeraccount`, and it'll pull the
+onos-config code from `mygithubaccount`. Using a personal docker account is not strictly necessary;
+images can also be built and tagged entirely locally.
+
Inspecting logs
---------------