Add support for specifying git revision on Import Resources form

[AlanGreene]

Is your feature request related to a problem ?

Import Resources is currently hardcoded to import from the master branch of the repository specified. This means users cannot reference Tekton resources from other branches or take advantage of standard git versioning approaches (e.g. tags) to maintain their pipeline definitions when used with this feature.

Describe the solution you'd like

The Import Resources form should include input(s) to allow specifying the git revision desired.

See tektoncd/pipeline#2320 and https://github.com/tektoncd/pipeline/blob/master/docs/resources.md for details of the revision and refspec (optional) fields on the git PipelineResource.

Also tektoncd/pipeline#2822 for related discussion about defaults.

Describe alternatives you've considered

Additional context

[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]

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]

@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.

[AlanGreene]

/remove-lifecycle rotten
/reopen

[tekton-robot]

@AlanGreene: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

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.

[AlanGreene]

Import Resources is currently using a git PipelineResource. We may want to consider removing this and moving to an alternative implementation given PipelineResources are still alpha and may be deprecated and removed in a future Pipelines release.

There's a git-clone Task in the catalog that was designed as a replacement for the git PipelineResource. It supports revision, refSpec, and a number of other params that may be useful.

How would we use this Task? Bundle the Task with the Dashboard install as we used to do with our pipeline0?

[AlanGreene]

Another approach to using the git-clone Task without having to ship it with the Dashboard would be to use Tekton Bundles, however support for this is currently disabled by default in Tekton Pipelines tektoncd/pipeline#3661. There's also a feature request to have Tasks from the catalog automatically published as bundles tektoncd/catalog#577