We are going to upgrading ABP 8 to ABP 10 (Micro Services template)
I noticed that since ABP9, each MicroService project layout is simplified,
Now it becomes
But I feel like for a system already go lives for years, It is safer to continue using legacy ABP Cli doing the upgrade so that the projects layout would not change significantly.
ABP would keep upgrading legacy ABP cli, right? Any suggestion?
[maliming] said: hi
Switch Ocelot to YARP for the API Gateway
Until this version, ABP Commercial was using the Ocelot for the API Gateway, in the Microservice Startup Template. Since the Ocelot library is not actively maintained, we have searched for an alternative and decided to switch from Ocelot to YARP for the API Gateway. YARP is maintained by Microsoft and is actively being developed and seems a better alternative than Ocelot and provides the same feature stack and even more.
You can read the Migrating to YARP documentation for migrating your existing microservice application's API Gateway from Ocelot to YARP.
We have made the all related changes in the Microservice Startup Template, and also updated the documentation, which you can read here. https://abp.io/docs/commercial/8.0/startup-templates/microservice/gateways
https://abp.io/community/articles/abp.io-platform-8.0-rc-has-been-published-3d8z8i16#switch-ocelot-to-yarp-for-the-api-gateway&gsc.tab=0
Is your project a microservice?
Thanks.
Yes
We have a project currently is ABP 8.1.3 which still uses Ocelot, we are going to upgrade it to ABP 10.1.0, do we have to upgrade to Yarp? Recommendation?
I forgot which is the first version of ABP that replace Ocelot to Yarp, do you know about it?
I noticed that ABP 9 introduced "Entity Cache", if a an Entity has navigation properties, for example, a Product has a list of Orders. If I register Product for entity cache, when Order is changed or added to the product, would the cached product has latest orders list?
thank you very much it's very helpful.
We are using QA environment for automation test.
For above test account, could user password set to never expire?
When an tenant has 2FA enabled, it's not able for automation API testing. So when a tenant has 2FA enabled, could particular user account has it disabled? If yes, which database table shall I check the value? Is there admin UI for it?
Or do you have any other better idea for backend API automation testing?
We can close this ticket. Finally identified it's our code issue, somewhere try the exception and convert it to some other type's exception.
