Rudder

I tried to create several plugins using a "hack" to create ncf techniques under specifics directives categories.

Here is the global fs schema:

[root@server configuration-repository]# ls -l techniques/CIS_plugin/Set_permissions/1.0/
total 8
-rw-rw-r--. 1 root rudder 2653 18 déc.  09:38 metadata.xml
-rw-rw-r--. 1 root rudder 1224 18 déc.  09:38 rudder_reporting.cf

[root@server configuration-repository]# ls -l ncf/50_techniques/Set_permissions/Set_permissions.cf
-rw-rw----. 1 ncf-api-venv rudder 1650 18 déc.  09:38 ncf/50_techniques/Set_permissions/Set_permissions.cf

[root@server configuration-repository]# ls -l techniques/ncf_techniques/ | grep Set_permissions
lrwxrwxrwx. 1 root rudder  29 18 déc.  09:37 Set_permissions -> ../CIS_plugin/Set_permissions

This works super fine, I then create the given directive via some API scripts.
But, when I try to use this technique to create a new directive via the webapp, I always end up with the following error:

⇨  Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, Set_permissions, 1.0),rudder_reporting.cf)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects.;Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, Set_permissions, 1.0),rudder_reporting.cf)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects.

It seems like something using TechniqueResourceIdByPath cna not read the given path since it is under a symlink. It may come from git if we are reading from it since it will not add files under symlink.
Also, if I change the technique via the technique editor, the changes are saved, the files are changed but the directive page does not and will not display the changes (in the parameters for instance).