Make instructions in DEVELOPMENT guide work

[bobcatfish]

Expected behavior

Folks who try to follow along with our DEVELOPMENT.md should be able to actually run the commands.

(of course one way to meet this would be to delete the stuff we don't have yet, but I think it would put us in a great position to add all the supporting code we need to just make it work!)

Actual behavior

We have no code yet, so most of the contents of the DEVELOPMENT.md would not work.

I copied most of the DEVELOPMENT.md contents from https://github.com/tektoncd/pipeline/blob/master/DEVELOPMENT.md but didn't copy the supporting code (e.g. hack dir).

Some things I noticed that we could probably make work fairly easily, that would set us up nicely:

• adding the supporting scripts in the hack dir (update-deps, update-codegen)
• making update-codegen work by adding an empty or nearly empty _type.go file.
• getting ko apply -f config/ to work, an easy way to do this would be to copy a lot of the config from https://github.com/tektoncd/pipeline/tree/master/config maybe without the bit to deploy the controller and webhook cuz we don't have those yet
• Note that in Create a skeleton controller that does nothing #8 we'll create a skeleton controller and in Create a skeleton webhook that does nothing #9 we'll create a skeleton webhook

Additional info

• DEVELOPMENT.md is being added in Add initial docs 📝 #2
• This is going to require vendoring in a lot of the deps we need; the first step to make that work will be to figure out what to vendor to get update-deps.sh (or similar) to work.

[ncskier]

@bobcatfish to clarify, are we making it possible to install triggers independently from pipeline? If so, we'll need to add yaml for our own Namespace, ClusterRole, ServiceAccount, ClusterRoleBinding, etc. (some of these might be duplicates from pipeline; for example, the Namespace could be the same yaml file that's in pipeline?).

[ncskier]

I followed up with @bobcatfish about my previous comment, and I will proceed with this issue under the assumption that users can install triggers without having installed pipelines (although they will work best together). The triggers project will be installed into the tekton-pipelines namespace, but will use its own ServiceAccount.

[ncskier]

Closing this issue now that ko apply -f config/ works, the hack directory (with update-deps and update-codegen) works, and the skeleton controller & webhook exist.

Relevant PRs:

• docs update: Remove outdated warning notes in the DEVELOPMENT doc #30
• skeleton webhook: init-webhook #21
• skeleton controller: Create a skeleton controller #18
• types & hack code: Create new types and add initial generated code #17

[bobcatfish]

niiiiice 🎉