Hi, We actually have a REST API to delete a given label. Also, for the initial version, we thought of simplifying the label scenario. In later releases, we can add an UI support to manage labels.
I don't think we need to bring the permission model unless we provide gateways per user/group. In the store side, we have introduced an extension point to filter labels depends on the user. The story behind the label scenario is to simplify the dynamic gateway registration. For an example, consider a deployment which has multiple APIs deployed in public and private gateways. Now our requirement is to spin a new gateway in Singapore region and serve a particular API. What we need to do is to spin a gateway in that region with the new label and re-publish the API with the new label. We have used labels to manage gateways in this scenario. If we are not allowing dynamic label registration, we can have admin API for labels. Yes, we can ship default labels. But when we need to bring up a new gateway, we have to make the REST calls to register the gateway. This is kind of a user interaction or maybe we can automate this based on the use case. But with dynamic label registration, we don't need to do anything specifically. If we consider a container scenario, we only need to pass an environment variable with the new label name to the container to spin up a new gateway container in a new region. 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
