Rudder

Historically, techniques had their ID derived from their path using the template ${categoryPart}/${techniqueName}/${techniqueVersion}/[metadata.xml & all]

Since we have a technique editor, the technique ID is created one time and stored in the serialized format of the technique descriptor: once upon a time, technique.json, and in Rudder 8.0, technique.yml.
We used to have guards to ensure both view of technique Id were matching. The guards were ensured by the webapp.

Now in Rudder 8.0, techniques are coming and going without webapp management: developpers (out of rudder core dev) will want to add theirs techniques in Rudder from sources without having to use the editor. And there isn't any reason they know about the constraint on directory path.

So in the short term, we need to add more guards in webapp, at the stage where technique descriptor is read/loaded/used to compile metadata.xml to check if things match or not ; and in the long term (not that ticket), we need to change technique historical naming scheme and keep only one technique id (the one in the descriptor).