Documentation error on hello-world example

[pmjordan]

If the hello-world example is deployed before minikube tunnel is running then the turandot service list shows url: http://0.0.0.0:80 not url: http://'<'unknown'>':80 as it did previously.
At least in my environment the output was not updated once minikube tunnel was started. The log messages were:

ERROR [turandot-operator.processor.services] requeuing unfinished work item (36 time) workspace/hello-world: GoError: topology_template.outputs["url"].value: call to tosca.function.get_attribute("hello-world","web","status","loadBalancer","ingress",0,"ip") failed because nested capability "web" attribute "status.loadBalancer.ingress" not found in "hello-world" at internal:tosca.lib.traversal:145:15(58)

INFO [turandot-operator.controller] Event(v1.ObjectReference{Kind:"Service", Namespace:"workspace", Name:"hello-world", UID:"ee674c74-e859-4fb7-996a-720084ad4cca", APIVersion:"turandot.puccini.cloud/v1alpha1", ResourceVersion:"13405", FieldPath:""}): type: 'Warning' reason: 'CloutUpdateError' Service Clout update error: GoError: topology_template.outputs["url"].value: call to tosca.function.get_attribute("hello-world","web","status","loadBalancer","ingress",0,"ip") failed because nested capability "web" attribute "status.loadBalancer.ingress" not found in "hello-world" at internal:tosca.lib.traversal:145:15(58)

From my viewpoint I would be happy to fix this in the documentation by starting the tunnel before the turandot service.

[tliron]

Thanks! Yes, this is indeed a change due to the attribute now having constraints (it must be an actual IP address, not an arbitrary string). No worries, I will fix this quickly on my end. Thanks for reporting.

[pmjordan]

You might also want to start the tunnel in lab/start so that it is ready for lab/test