Project

General

Profile

Actions

User story #17133

closed

Rudder should be able to read techniques by itself and not rely on legacy ncf rest api

Added by Vincent MEMBRÉ about 4 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
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


Subtasks 8 (0 open8 closed)

User story #17134: Adapt technique editor to not call ncf api and add method to generate data for RudderReleasedFrançois ARMANDActions
Bug #17206: missing ng-init after rebaseReleasedFrançois ARMANDActions
Bug #17209: wrong format of generic methods fileReleasedAlexis MoussetActions
User story #17135: Remove ncf rest apiReleasedFrançois ARMANDActions
Architecture #17166: Remove packaging of ncf apiReleasedAlexis MoussetActions
Bug #17185: Parent broke apache syntaxReleasedVincent MEMBRÉActions
Bug #17197: ncf api file is still packaged, breaking buildsReleasedAlexis MoussetActions
User story #17208: create generic method file missingReleasedFrançois ARMANDActions
Actions #1

Updated by Vincent MEMBRÉ about 4 years ago

  • Subject changed from Remove technique editor dedicated API to Rudder should be able to read techniques by itself and not relay on legay ncf rest api
Actions #2

Updated by Vincent MEMBRÉ about 4 years ago

  • Category set to Web - Config management
  • Target version set to 6.1.0~beta1
Actions #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Subject changed from Rudder should be able to read techniques by itself and not relay on legay ncf rest api to Rudder should be able to read techniques by itself and not rely on legacy ncf rest api
Actions #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #6

Updated by Vincent MEMBRÉ about 4 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2900
Actions #7

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from In progress to Pending release
Actions #17

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.0~beta1 which was released today.

Actions #18

Updated by François ARMAND almost 4 years ago

  • Fix check changed from To do to Checked
Actions

Also available in: Atom PDF