Unable to get Runnable Tekton logs in TAP 1.3 and earlier with a custom stage name

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

In 1.3 and earlier the views in the UI were selected based on the “stage name”. If the stage is named source-tester, customer is able get the tekton logs. But if it's named with a seperate custom stage name. They will not get tekton logs.
In 1.4+, TAP looks at the GVK of the resource thats stamped out.

Environment

Product Version: 1.3

Resolution

As the tekton logs will only be displayed if the stage is called source-tester in 1.3 and earlier. The suggestion to the customer is to either upgrade to TAP 1.4 or rename the stage to source-tester. This has been fixed in TAP 1.4.