Hello everyone,
the Malawi team has recently contributed a change to the requisition service that allows service-level tokens to retrieve data for certain endpoints. This is a change that is required by our custom reports and those endpoints are used from our custom module. Unfortunately, we cannot work on a snapshotted version of the requisition service as it also brings the changes required to the latest reference data (with orderables refactor) for which we are not ready just yet and which won't work with ref data 5.0.0. Would it be possible to have the Requisition service 3.1.3 release, containing just the changes up to enabling service-level tokens?
Regards,
Sebastian Brudzinski.
Sebastian
Brudziński
Software Developer / Team Leader
sbrud...@soldevelo.com
SolDevelo Sp. z o. o. [LLC]
Office: +48 58 782 45 40 / Fax: +48 58 782 45 41 Al. Zwycięstwa 96/98 81-451, Gdynia
http://www.soldevelo.com
Place of registration: Regional Court for the City of
Gdansk KRS: 0000332728, TAX ID:
PL5862240331, REGON: 220828585, Share capital:
60,000.00 PLN
Hello,
I know that we didn't want to worry about inter-service dependencies for now, but I believe this case highlights a real issue - a PATCH change in requisitions requires a MAJOR update to reference data. For implementations, the reality is that this is not a PATCH change, it is a MAJOR change - the requisition version means very little here.
I think that we should start thinking about this - it would be
easy to hack up a solution that gets the version of the reference
data and makes the call based on its version - until we deprecate
support.
Going through the bing bang release with reference data might
also be a solution that makes this problem go away - but it won't
eliminate it completely.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/fa5a267e-9db9-2214-d480-8050907e4e7d%40soldevelo.com.
For more options, visit https://groups.google.com/d/optout.
+1 for adding dependency info into the README of each component. That’s a simple thing we can update each time we release, just like we update the CHANGELOG. Then those README files will be a historical record of which component versions worked with which others. I think that’s a simple task with a big benefit for this situation.
-Brandon
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/6238674b-b909-43c9-9b3e-1ef6520aa575%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/EDD525B8-9E0D-4E2C-845F-11A113E0630E%40villagereach.org.
For more options, visit https://groups.google.com/d/optout.