On Wed, Aug 8, 2018 at 7:33 PM Nuwan Dias <[email protected]> wrote: > How about introducing it as an annotation (custom of course) to the > Ballerina code itself? > This seems to be the most easiest way, But one micro gw can have multiple apis , then annotation have to be copied for each api. Other way is to add it to micro-gw conf (toml) while copying it to the distribution when building the distribution.
> > On Wed, Aug 8, 2018 at 5:46 PM Fazlan Nazeem <[email protected]> wrote: > >> Hi, >> >> Is there a way to extract the microgateway label from the runtime? This >> is because we need to publish this information to the Stream Processor for >> analytics. Although we do not have any charts which filter statistics >> depending on the label, this may come up as a requirement in the future. >> Additionally, there should be some mechanism to know what label is >> associated with each microgateway. Once the micro-gateway is generated, >> this information doesn't seem to be retrievable. >> > And also micro gateway can be built without label also. It can fetch an api from name and version, so there won't be label at that time. Then we have only the project name. Can't we use project name for this. > >> Currently, the value for the label field is predefined in the source >> code. According to an offline chat with Malintha, we may have to burn the >> label into the microgw-conf file during gateway building phase or persist >> this info in some other means. Any suggestions? >> > >> -- >> Thanks & Regards, >> >> *Fazlan Nazeem* >> Senior Software Engineer >> WSO2 Inc >> Mobile : +94772338839 >> [email protected] >> > > > -- > Nuwan Dias > > Director - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- Rajith Roshan Senior Software Engineer, WSO2 Inc. Mobile: +94-7 <javascript:void(0);>17-064-214
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
