Actions
Bug #10397
closedUser story #6244: Automatic directive naming
Missing "default-directive-names.conf" example file
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
The parent task added the possibility to have a default naming scheme in Rudder UI for new directives (by version if wanted).
We should add the default example file so that it is on all Rudder fresh installation.
I'm not sure if we prefer to add it in Rudder and copy it during packaging, or just add it in rudder-techniques repository, (in "techniques" directory).
The file could look like:
$cat techniques/default-directive-names.conf # # This file contains the default name that a directive gets in Rudder UI creation pop-up. # The file format is a simple key=value file, with key being the techniqueName # or techniqueName/version and the value being the name to use. # An empty value will lead to an empty default name. # For a new Directive, we will try to lookup "TechniqueName/version" and if not # available "TechniqueName" from this file. If neither key is available, the # pop-up will use the actual Technique name as default. # Don't forget to commit the file to have modifications seen by Rudder. # # Default pattern for new directive from "userManagement" technique: userManagement=User: <name> Login: <login> # For userManagement version 2.0, prefer that pattern in new Directives: userManagement/2.0: User 2.0 [LOGIN]
Actions