Hi Lakmal, I think we have to rethink about the general use-case scenario. I have missed some of the points during the offline discussion we had.
Let me first explain the current model. The label is a must for a gateway and gateway can have only one label. When you are spinning a new gateway, you can provide a label name with access urls. We manage access urls of the gateways using labels. For an API, you can select multiple labels. When you select an API in API Store, based on the attached labels to the API, we display the gateway endpoints where you can use to invoke the API. For the general use case, if we are not mandating or introducing a default label, we need to find a way of displaying gateway urls. One of the options I have in mind is to introduce a default label. It has the access url of the gateway. Still, we can go with the admin API and move away from the dynamic gateway registration. This is more suitable in order to introduce the permission model to the labels. The label selection is not mandatory when creating an API. If the user hasn't selected any label, we can attach the default label. Thank you! -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
