Hi Uvindra, We are having same issue and being solved in AppM 1.1.0. We were informed that ES 2.0 has a grouping capability, exposed by registry. So we may be exploit that to correlate versions. We plan to back-port some ES 2.0 functions to ES 1 branch to get this done.
Sajith (AR) working on this. Cheers, Ruwan On Wed, Jul 22, 2015 at 12:21 PM, Uvindra Dias Jayasinha <[email protected]> wrote: > This applies to API Manager 1.9.0, but this is true for previous versions > as well. When trying to fix the following ticket[1] I came across this > scenario, > > 1. API named *"foo"* with versions *"1.0.0"* and *"2.0.0"* has > existing subscriptions. > 2. Create a new version of the same API *"3.0.0"* from *"2.0.0"*. > 3. Publish API *"foo:3.0.0"* with the "Require Re-Subscription" > option disabled. > 4. What should happen is that the subscriptions of *"foo:2.0.0"* > should be applied to *"foo:3.0.0" *automatically > > > The problem is step *2 *and *3* above are separate so there is currently > no association between *"foo:2.0.0"* and *"foo:3.0.0"*. > > So how do we determine which API version *"foo:3.0.0"* was created from > so that we can transfer that APIs subscriptions at the time of publishing? > > Is there a way to do this without adding a new attribute to the newly > created API to indicate whihc version it was copied from? > > [1] https://wso2.org/jira/browse/APIMANAGER-3971 > -- > Regards, > Uvindra > > Mobile: 777733962 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ruwan Abeykoon* *Architect,* *WSO2, Inc. http://wso2.com <http://wso2.com/> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 777739736
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
