Retired means it never come back right. So what is the purpose of maintaining some additional data. Context and version can be maintain to avoid another API creation with same name context. IMO other than that we do not need anything.
Thanks, sanjeewa. On Mon, Aug 3, 2015 at 6:46 PM, Nuwan Dias <nuw...@wso2.com> wrote: > I don't think we should be removing resources and scopes. Because we're > not deleting the API here but only retiring it. If the publisher wants to > bring it back online he can do so but he would have lost all subscriptions > by then, which is fine IMO. > > Thanks, > NuwanD. > > On Mon, Aug 3, 2015 at 4:31 PM, Sanjeewa Malalgoda <sanje...@wso2.com> > wrote: > >> +1 if its temporary outage then that should be blocked. Deprecate and >> retire means they will never come back. >> So we may clean all data associated with given API. Lets make sure we >> remove all data including subscriptions, resources, scopes etc >> >> Thanks, >> sanjeewa. >> >> On Mon, Aug 3, 2015 at 3:44 PM, Nuwan Dias <nuw...@wso2.com> wrote: >> >>> We should get confirmation before he retires to make sure he knows what >>> he's doing. >>> >>> I don't think retiring an API temporarily is a valid scenario. Retiring >>> means he's removing it from the runtime totally. So if there are existing >>> users, they'll get service outages. He also has options to Block the API or >>> even deprecate it. He should go for one of those options if he want's to do >>> something temporarily. >>> >>> Thanks, >>> NuwanD. >>> >>> On Mon, Aug 3, 2015 at 3:39 PM, Abimaran Kugathasan <abima...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> I'm working on JiRA [1] >>>> >>>> When we try to delete a retired API from API Publisher, if that API has >>>> subscriptions, APIM won't allow to delete that API. >>>> >>>> As a solution, APIM can remove those subscription when retiring the >>>> API. But, If a API owner temporarly retired the API and later in some >>>> point, he re-published that API. Since APIM removed the subscription while >>>> retiring that API, All the users have to re-subscribe to that API once it's >>>> back to published state. It will loose it's earlier subscriptions. >>>> >>>> How should we handle the API's state in this case? Are we going to >>>> suggest re-subscription the API or We will keep another state for the API? >>>> >>>> Please provide your valuable feedback. >>>> >>>> >>>> [1] : https://wso2.org/jira/browse/APIMANAGER-3964 >>>> >>>> -- >>>> Thanks >>>> Abimaran Kugathasan >>>> >>>> Software Engineer | WSO2 Inc >>>> Data & APIs Technologies Team >>>> Mobile : +94 773922820 >>>> >>>> <http://stackoverflow.com/users/515034> >>>> <http://lk.linkedin.com/in/abimaran> >>>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>>> <https://twitter.com/abimaran> >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Technical Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> >> *Sanjeewa Malalgoda* >> WSO2 Inc. >> Mobile : +94713068779 >> >> <http://sanjeewamalalgoda.blogspot.com/>blog >> :http://sanjeewamalalgoda.blogspot.com/ >> <http://sanjeewamalalgoda.blogspot.com/> >> >> >> > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
