The YARP resource is a nice way to convert the Tye "ingress" node and I am using it in the latest application I'm migrating from Tye to Aspire.
This conversion made me wonder if it's possible to give the Yarp resource a OT identity so that it's shown in traces.
Then I'm proceeding to convert my other application. This one uses two distinct "ingress" nodes and, as I can see, there is a "Single" check to make sure there is only one Yarp resource. Is there a way to remove this constraint?
The YARP resource is a nice way to convert the Tye "ingress" node and I am using it in the latest application I'm migrating from Tye to Aspire.
This conversion made me wonder if it's possible to give the Yarp resource a OT identity so that it's shown in traces.
Then I'm proceeding to convert my other application. This one uses two distinct "ingress" nodes and, as I can see, there is a "Single" check to make sure there is only one Yarp resource. Is there a way to remove this constraint?