Forgot about the credentials thing, thanks for the reminder :( So basically there is a default (internal) store we always publish to, and then additional stores we can publish to as a separate action. If yes. +1 to that, covers most of use cases I think.
Isabelle. __________________________________________________ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri Lanka) +94 (0)774777663 On Sep 17, 2013, at 10:28 AM, Sumedha Rubasinghe <sume...@wso2.com> wrote: > We have decided to move this to a new tab in API detail page. Only APIs in > 'PUBLISHED' status can be pushed into other external stores. @ the point of > publishing an API, it will be pushed into internal store as before. > > > On Tue, Sep 17, 2013 at 1:29 PM, Isabelle Mauny <isabe...@wso2.com> wrote: > Hi Chamara, > > IMHO, this is a publishing decision - i.e. it's the responsibility of the > publisher to do this (i.e option 3) . There are a couple use cases to > consider here > > a) A publisher needs to be able to publish the API to multiple stores. this > publication is independent from the runtime publication (i.e. gateway > configuration) . Moreover they need to be able to publish to additional store > at any moment - Consider an API which is published in the company store to > start with and then is pushed to an external catalog when this is approved. > In other words, publish to store shall be a self-contained action as well. > b) We need to plan for additional metadata to be captured for those external > catalogs ( what they are asking for might be different than what we capture > out of box). > > And finally security : where/when do we capture/store the credentials to > connect to an external store ? > Isabelle, > This is coming in as a configuration as per the discussion in > http://markmail.org/message/ky7veo2uud4woh25. > > > Isabelle. > > > ------ > Isabelle Mauny > Director, Product Management; WSO2, Inc.; http://wso2.com/ > email: isabe...@wso2.com - mobile: +34 616050684 > > > On Tue, Sep 17, 2013 at 7:54 AM, Chamara Ariyarathne <chama...@wso2.com> > wrote: > Ping..! > > > On Mon, Sep 16, 2013 at 10:29 AM, Chamara Ariyarathne <chama...@wso2.com> > wrote: > Three possibilities are while; > > 1. Creating the API > 2. Editing the API > 3. Publishing the API > > (See attached screenshots) > > 1. If the option is given at the place of Creating the API, the API need to > be created in the external store as well in Unpublished state. > > 2. If the option is given at only Editing the API, it is not straightforward. > > 3. If the option is given at Publishing the API / Lifecycle changing place, > everytime the api is changed, it will have to be published. > > The feature seems buggy at the moment. But to create useful bugs, the > scenario need to be clearly defined. > > Also the scenarios need to be planned the way it support publishing to > external non-wso2 apistores as well. > > -- > Chamara Ariyarathne > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; +94772786766 > > > > -- > Chamara Ariyarathne > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; +94772786766 > > > > > -- > /sumedha > b : bit.ly/sumedha
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
