tanzu apps workload get doesn't show the workload URL

[kartiklunkad26]

Bug Report

When I install the tanzu apps cli plugin, and use the tanzu apps workload get command, I want to see the URL of my deployed workload. But that doesn't happen right now.

Expected Behavior

I expect to get the workload URL when I run tanzu apps workload get

Steps to Reproduce the Bug

1. Follow the App Toolkit Package README for installing, configuring and creating Tanzu workload
2. Then run tanzu apps workload get, you'll see the below output.

Screenshots or additional information and context

---
lastTransitionTime: "2022-03-30T18:21:36Z"
message: ""
reason: Ready
status: "True"
type: Ready

Pods
NAME                                     STATUS      RESTARTS   AGE
tanzu-simple-web-app-build-1-build-pod   Succeeded   0          4d19h
tanzu-simple-web-app-build-2-build-pod   Failed      0          47h

Environment Details

• Build version (tanzu version): TCE v0.11
• Deployment (Managed/Unmanaged cluster): unmanaged-cluster
• Infrastructure Provider (Docker/AWS/Azure/vSphere): Docker
• Operating System (client): MacOS

Cross-posted Apps CLI Plugin issue

vmware-tanzu/apps-cli-plugin#58

[kartiklunkad26]

cc: @atmandhol @heyjcollins @rashedkvm

[kartiklunkad26]

@scothis's comment in the Tanzu Apps CLI Plugin repo:

The CLI is looking for the label carto.run/workload-name={the-workload-name} that isn't defined on the Knative Service. Without the label, the CLI has no ability to link together resources created because of the workload from pre-existing resources.

community-edition/addons/packages/app-toolkit/0.1.0/test/example_sc/kpack-templates.yaml

Line 158 in bea08ce

metadata:

Looks like this is a bug in the usage example supply chain in our App Toolkit package. Updating the label for App Toolkit team to work on it.

Keeping the bug open until we resolve it.

[joshrosso]

@kartiklunkad26 if all goes well, is this something we plan to address in v0.12.0?

And would you like to assign and owner to this work if so?

[kartiklunkad26]

This will likely be resolved with a documentation update itself that would need to be backported to TCE v0.11 docs. @ryanmattcollins will be making that. Assigning to him now.

This will not be a issue for TCE v0.12.

[kartiklunkad26]

@ryanmattcollins and I tried to fix this, but realized it gets complicated because adding the label replaces the other existing labels.

Given we will have a basic supply chain package as part of App Toolkit in v0.12. This bug will get addressed at that time.

Keeping it open, but will be addressed in v0.12.

[jpmcb]

@kartiklunkad26 - do you think this will be able to get into our v0.12.0? If not, can we push this to v0.13.0?

[jpmcb]

Also cc @ryanmattcollins for visability

[kartiklunkad26]

This is now working in TCE v0.12.