Add new action for PipelineRun - Edit and Run

[marniks7]

Changes

Add new action for PipelineRun - Edit and Run.
Solves: #2437

• Action from list of PRs
  
• Action from single PR
  
• Result of Edit and Run click:
  
• YAML page loading while PipelineRun is not fetched yet
  

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Add new feature: ability to edit and run new pipeline (completed or failed or running)

[tekton-robot]

Hi @marniks7. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[marniks7]

/kind feature

[AlanGreene]

Thanks for the PR @marniks7. Overall it looks pretty good. I've left a few suggestions, let me know if you have any questions.

As we discussed on one of the previous issues / PRs I'd like to avoid adding more PipelineRun specific code into the YAML editor so we can more easily reuse it for other resource types in the near future.

[marniks7]

Didn't want to create separate PR for an issue with pipelinePendingStatus, in yaml it was status: !<tag:yaml.org,2002:js/undefined>.
It is fixed.

P.s. PR ready for review

[AlanGreene]

/ok-to-test

Please also squash your commits when done

[AlanGreene]

Thanks @marniks7, this is looking pretty good now.

[AlanGreene]

Thanks @marniks7. This will be included in the v0.32 release due in the next few days.
/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlanGreene

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AlanGreene]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment