The name for the values in PipelineParams should be descriptive and should be pluralizable without causing laughter.
The current name is PipelineParams and code-generator pluarlizes this as pipelineparamses #114 (https://github.com/kubernetes/code-generator/issues/53)

PipelineParams used to contain a grab bag of various parameters, but many of these are being moved into Resources instead. At the moment it has been reduced to containing only:
Some name ideas:
PipelineConfigResultConfig, ResultStore@scothis has pointed out a related fix in knative/serving which is actually pretty simple/easy to add: https://github.com/knative/serving/blob/22e3cb0f057daf224ef3af5cc37feb9b152f880e/hack/update-codegen.sh#L34
So we can do the same thing for PipelineParamses - but I still think we should pick better names? Maybe we can just fix PipelineParamses and resolve this issue for now tho 馃
Can we rename the type to PipelineParam and then the plural of it would be PipelineParams? All the other existing types have singular names (Task, Resource, ...)
or even change the name completely, for example PipelineConfiguration
This has been vexing me lately as I try to write up and explain the Pipeline CRD model to others, particularly to anyone with a Jenkins background, since PipelineParams sure sounds like it's where you define parameters for a pipeline, but it's in fact just a narrow scope of parameter types, and not ones that change from run to run (unlike Jenkins' job parameters). So I'm a 馃憤 for PipelineConfig or some variant thereof.
@abayer looks like in #263 we _might_ actually define arbitrary pipeline parameters too :O
PipelineConfig still seems like a better name tho :thinking:
/assign @pivotal-nader-ziada