Architecture #19037 closed
Refactor the system techniques by component
Added by Félix DALLIDET over 4 years ago.
Updated almost 4 years ago.
Category:
System techniques
Description
Currently the system techniques are not designed to be split. This is more and more a problem if we want to be able to manage easily each rudder component in a separated way. We should try to refactor the current techniques and organize them by Rudder role and service: root/relay/agent and apache/relayd/jetty/slapd/agent.
Assignee set to Félix DALLIDET
Status changed from In progress to Pending technical review
Assignee changed from Félix DALLIDET to Alexis Mousset
Pull Request set to https://github.com/Normation/rudder-techniques/pull/1652
Status changed from Pending technical review to In progress
Assignee changed from Alexis Mousset to Félix DALLIDET
Status changed from In progress to Pending technical review
Assignee changed from Félix DALLIDET to Alexis Mousset
Pull Request changed from https://github.com/Normation/rudder-techniques/pull/1652 to https://github.com/Normation/rudder-techniques/pull/1659
Status changed from Pending technical review to Pending release
This bug has been fixed in Rudder 7.0.0~beta1 which was released today.
Related to Enhancement #19573 : Correct policy write unit tests to use new system techniques added
Status changed from Pending release to Released
Category set to System techniques
Also available in: PDF
Atom