Hi Malintha

Do we have multiple tier.xml files per group ?

On Tue, Dec 1, 2015 at 7:41 AM, Sanjeewa Malalgoda <sanje...@wso2.com>
wrote:

>
>
> On Mon, Nov 30, 2015 at 11:05 PM, Malintha Amarasinghe <malint...@wso2.com
> > wrote:
>
>> Hi All,
>>
>> With the new REST API for API Manager we are exposing a resource /tiers
>> for retrieving/adding/updating tiers. Additionally we have a sub resource
>> /tiers/{tier-id}.
>>
>> As of now, we have been using tier name as the tier-id. It did not give
>> problems as it could be used to identify a tier uniquely as we were
>> maintaining a single set of tiers for all types (API, application and
>> resources)
>>
>> With the new tier grouping feature, we have defined tiers per app/API and
>> resource separately. We are currently using separate names, but still the
>> admin can modify the tiers.xml files and define tiers with same name for
>> those types, hence identifying tier from tier name can be ambiguous.
>>
> Ideally we will not use same set of names across application, api and
> resources. We agreed to use different set of names for each tier types,
> So i think this will not cause any problem.
>
> Thanks,
> sanjeewa.
>
>>
>> Because of this problem, would we be able to continue using tier name as
>> the tier id? Can you please give a better suggestion.
>>
>> Thank you,
>> Malintha
>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> <http://sanjeewamalalgoda.blogspot.com/>blog
> :http://sanjeewamalalgoda.blogspot.com/
> <http://sanjeewamalalgoda.blogspot.com/>
>
>
>


-- 

-- 
*Joseph Fonseka*
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka

* <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to