Congrats! Sounds like a huge step forward. Is it time to upgrade apiman on fabric8? --Kurt On Tue, Jun 27, 2017 at 3:03 PM, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > > Hi All, > > I'm delighted to announce Apiman 1.3.1.Final is out, with a few notable > new features and improvements [1]. > > ## 3scale-related functionality > > You can now use the Apiman Gateway with the 3scale Manager/UI as an > alternative to the Apiman Manager/UI![2] > > Using an overlay file you can augment your 3scale APIs with apiman > policies. There will hopefully be an opportunity for a more cohesive and > deeper integration with 3scale in the near future. Your feedback and demand > will drive this; I hope as many people try it out this functionality as > possible! > > The new 3scale registry and plugin can perform all of the usual 3scale > functions, such as auth, reporting, metrics, and rate-limiting; with the > addition breadth of apiman's policies and pluggable functionality. The one > exception is that 3scale OAuth is currently not implemented (apiman's OAuth > plugins work as normal). > > I'll be providing some blogposts over the coming days to demonstrate the > new features in a more digestible form, but the documentation is available > already. Just download the Vert.x distro and follow the instructions: > > > https://apiman.gitbooks.io/apiman-installation-guide/installation-guide/v... > > > https://apiman.gitbooks.io/apiman-installation-guide/installation-guide/r... > > Expect some tooling soon to make generating JSON configurations for > headless and 3scale registries easier! > > ## Bug-fixes & Improvements > > A good number of bugs were squashed in this release. Please try it out and > let us know if your issues persist (if you had any!). > > The HTTP codes returned in error cases have been improved, including > connection issues (e.g. DNS, timeouts, etc). You should no longer get HTTP > 500 for these, and the error messages should be more meaningful. Let us know > if there still seem to be issues in this area. > > There were a few issues with TLS on the Vert.x gateway that have been > improved (e.g. devmode was not working properly). In the near future we'll > look to provide some sort of self-signed certificate generation so that TLS > can be configured OOTB. As an added bonus, if you provide ALPN Boot, then > HTTP/2 should just work[3]. > > ## You can help! > > Please try the new functionality and let us know how you find it. Your > demand and feedback is extremely important to the future direction of this > project. > > ## Next > > Expect another release very soon with more functionality, configurability > and tooling. > > Some users have reported issues with the new GitBook documentation, so > I'll be looking to improve this. > > Regards, > Marc > > [1] The more eagle-eyed amongst you will no doubt have noticed that most > of this was actually released a few days ago. > [2] You will need 3scale SaaS or on-prem for this to work. > [3] More in a blog soon. > > _______________________________________________ > Apiman-dev mailing list > Apiman-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-dev > -- Kurt T. Stam twitter: @KurtStam google+: kurt.stam(a)gmail.com

Great job on the release, Marc! On Tue, Jun 27, 2017 at 3:03 PM, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > Hi All, > > I'm delighted to announce Apiman 1.3.1.Final is out, with a few notable > new features and improvements [1]. > > ## 3scale-related functionality > > You can now use the Apiman Gateway with the 3scale Manager/UI as an > alternative to the Apiman Manager/UI![2] > > Using an overlay file you can augment your 3scale APIs with apiman > policies. There will hopefully be an opportunity for a more cohesive and > deeper integration with 3scale in the near future. Your feedback and demand > will drive this; I hope as many people try it out this functionality as > possible! > > The new 3scale registry and plugin can perform all of the usual 3scale > functions, such as auth, reporting, metrics, and rate-limiting; with the > addition breadth of apiman's policies and pluggable functionality. The one > exception is that 3scale OAuth is currently not implemented (apiman's OAuth > plugins work as normal). > > I'll be providing some blogposts over the coming days to demonstrate the > new features in a more digestible form, but the documentation is available > already. Just download the Vert.x distro and follow the instructions: > > > https://apiman.gitbooks.io/apiman-installation-guide/installation-guide/v... > > > https://apiman.gitbooks.io/apiman-installation-guide/installation-guide/r... > > Expect some tooling soon to make generating JSON configurations for > headless and 3scale registries easier! > > ## Bug-fixes & Improvements > > A good number of bugs were squashed in this release. Please try it out > and let us know if your issues persist (if you had any!). > > The HTTP codes returned in error cases have been improved, including > connection issues (e.g. DNS, timeouts, etc). You should no longer get HTTP > 500 for these, and the error messages should be more meaningful. Let us > know if there still seem to be issues in this area. > > There were a few issues with TLS on the Vert.x gateway that have been > improved (e.g. devmode was not working properly). In the near future we'll > look to provide some sort of self-signed certificate generation so that TLS > can be configured OOTB. As an added bonus, if you provide ALPN Boot, then > HTTP/2 should just work[3]. > > ## You can help! > > Please try the new functionality and let us know how you find it. Your > demand and feedback is extremely important to the future direction of this > project. > > ## Next > > Expect another release very soon with more functionality, configurability > and tooling. > > Some users have reported issues with the new GitBook documentation, so > I'll be looking to improve this. > > Regards, > Marc > > [1] The more eagle-eyed amongst you will no doubt have noticed that most > of this was actually released a few days ago. > [2] You will need 3scale SaaS or on-prem for this to work. > [3] More in a blog soon. > > _______________________________________________ > Apiman-dev mailing list > Apiman-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-dev > > _______________________________________________ Apiman-dev mailing list Apiman-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/apiman-dev