Actions
User story #17133
closedRudder should be able to read techniques by itself and not rely on legacy ncf rest api
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Effort required:
Name check:
To do
Fix check:
Checked
Regression:
Description
Rudder does not now how to parse and analyse techniques from technique editor.
He knows how to treat a technique translated as json by the old remnants of the ncf rest api.
This api is slow, and there is lots of errors due to authentication between both apis (errors at webapp startup during migration because of jetty not ready or apache not ok, or something else)
We want to get rid of it and make Rudder autonomous on this part
We will now write a technique.json along within the technique files.and write a cache of parsed generic_methods. and read those files within Rudder when needed
We will also still need ncf python api to generate the files once and generate generic_methods at will
It can be enhanced with a caching system too
Actions