Provide manual step to create PipelineResources.

[sudhirverma]

currently, there is an interactive way to create a pipelineresources.

for example:

sudhirverma@Sudhirs-MacBook-Pro vscode-tekton % tkn res create
? Enter a name for a pipeline resource : xyz
? Select a resource type to create : git
? Enter a value for url :  https://github.com/openshift/pipelines-tutorial
? Enter a value for revision :  
New git resource "xyz" has been created

there should bee a way to create resources manually.

for example:

for creating git pipelineresources: tkn create -pipelinename 'xyz' -resourcetype 'git' -url 'githubUrl' -revision 'revision'
and the same type of command for 
 cloudEvent, cluster, git, image, pullRequest, storage

[piyush-garg]

/kind feature

[danielhelfand]

@sudhirverma Thanks for opening this issue. Would tkn resource create -f satisfy this use case? It allows you to create pipeline resources from a local or remote file of a pipeline resource. It was introduced in v0.6.0.

tkn resource create

Examples:
  
  # Creates new PipelineResource as per the given input
	tkn resource create -n namespace
	
  # Create a PipelineResource defined by foo.yaml in namespace 'bar'
	tkn resource create -f foo.yaml -n bar

[sudhirverma]

Hi, @danielhelfand when I am creating the resource from ymal.

for example:

tkn resource create -f pipeline/resources.yaml
resources.yaml is https://github.com/openshift/pipelines-tutorial/blob/master/pipeline/resources.yaml

output:
sudhirverma@Sudhirs-MacBook-Pro pipelines-tutorial % tkn resource create -f pipeline/resources.yaml 
PipelineResource created: api-repo

in resources.yaml there are four different types of PipelineResource but it creates only one while running the command tkn resource create -f pipeline/resources.yaml

cc: @dgolovin and @evidolob

[danielhelfand]

@sudhirverma Yes, so we do not at this time support multi resource file definitions. You would have to define each file individually and run tkn resource create -f for each. But I see your point and that was an overlook on our part that we should address. I think we should close this issue and open a new one around supporting multi resource file definitions.

[danielhelfand]

We have two issues open to replace this: #574 and #575. My personal preference is that we move away from a resource-specific creation approach and have create/apply be top level commands (e.g. tkn create versus having a create command for each resource).

Thanks for your comment in this issue though as it helped point out a big area of improvement for us. Feel free to weigh in on both of these issues to help push us in the right direction.