Better name for TriggerTemplate?

[bobcatfish]

Expected Behavior

TriggerTemplate is a pretty cool idea, which has the potential for being used beyond just in triggers b/c folks may have all kinds of circumstances in which they want to create instances of CRDs.

For example in #200 @skaegi is requesting a way to invoke a TriggerTemplate without any kind of EventListener and in the PipelineResource redesign I think TriggerTemplates could be a cool way to express how to create new instances of PipelineResources when created or mutated.

Actual Behavior

The name TriggerTemplates pretty much indicates this is part of triggering, and that's all its good for.

Additional Info

Some name ideas:

• ResourceTemplate <-- cuz we define how to create resources
• ResourceFactory <-- ah god the java - but factory isnt a bad name imo!
• ResourceCreator <-- i dunno
• Template <-- maybe too generic
• FromParamsToResource <-- .... okay ill stopp

Also in #200 @skaegi is proposing adding Run to the name of whatever this is called, might be interesting to brainstorm what the invocation of this thing could be called also.

p.s. @dibyom @wlynch @vtereso @ncskier @iancoffey if you folks agree with this, renaming before 0.2 could be good

[vtereso]

In deciding this, I think we should confirm whether we will or will not be opening templates to create any (or most) kind(s) of resources since that seems significant to the name (e.g. TektonTemplate vs ResourceTemplate).

Currently templates inject parameters as well as references via the $(uid) interpolation variable. In a world where run resources do not reference other event time resources (parameter passing only), the definition/function of a template would still creates Kubernetes resources, but not PipelineResources. For this reason, I think including names like ResourceFactory could be confusing. This aside, I am mostly indifferent about the naming.

[dibyom]

ResourceTemplate <-- cuz we define how to create resources

Currently, TriggerTemplates contain a field called ResourceTemplates containing the raw template

[dibyom]

/area api

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dibyom]

ref #697