On Wed, May 9, 2018 at 11:21 AM, Dinusha Dissanayake
wrote:
> Hi Chamin,
>
>
>
> On Tue, May 8, 2018 at 11:03 AM, Chamin Dias wrote:
>
>> Hi all,
>>
>> Thanks for the responses.
>>
>> This is to communicate a concern/conclusion regarding the flow (attaching
>> labels).
>>
>> *Using the UI (API P
Hi Chamin,
On Tue, May 8, 2018 at 11:03 AM, Chamin Dias wrote:
> Hi all,
>
> Thanks for the responses.
>
> This is to communicate a concern/conclusion regarding the flow (attaching
> labels).
>
> *Using the UI (API Publisher)*
>
> 1. We have decided to fetch the existing labels and provide the
Hi,
On Tue, May 8, 2018 at 6:10 PM, Sachini De Silva wrote:
> Hi all,
>
> Proposed resource structure is as below.
>
>
> /exports/apis:
>
+1. I think this looks more like generic export resource which is not
really specific for the ballerina gw feature. I think it is okay as we can
use this fo
Hi all,
Proposed resource structure is as below.
/exports/apis:
get:
x-scope: apim:api_export
produces:
- application/x-gzip
summary: Return apis categorized into a label.
description: |
This operation can be used to fetch APIs categorized into a certain
labe
Hi Dakshika,
Tags are for store users searching purpose. So that the subscribers can
search APIs based on the tags.
Labels are for the gateway level, which is in-fact micro-gateway level.
Say you have 100 APIs. But in the micro gateway, you only need to deploy a
subset of APIs. We can assign thos
Hi,
IMO its better if we share the real user story behind the creating labels
in gateway level. (Is it only for grouping purpose? )
Also whats the difference between current tags vs labels?
Regards,
*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, In
