Feature #322
closed
Ability to add custom fields and options
Added by Ashley Penney over 14 years ago.
Updated about 13 years ago.
Description
I would like the ability to predefine parameters in some fashion and then display them on the edit host page. I would like, if possible, to be able to define a default value and then choose between an entry box to change this or a drop-down with multiple pre-defined choices. I should also be able to say this is a mandatory parameter. Oh, and if we're really pushing it tying these parameters to included classes would be even better.
When adding a new host this would make it much easier to pass off the process to junior staff by making it impossible to miss a parameter or set it to the wrong value. If I include ldap then it would be nice for it to then require a value for $ldap_role for example.
- Tracker changed from Bug to Feature
@Paul - any ideas of how to implement this ticket?
thinking of this..
we would need to create some sort of metadata inside the module, foreman could read that file, and present dialogs accordingly...
an example for such file:
Name |
Type |
Description |
default value |
port |
integer |
port used for app X |
80 |
what do you think?
That sounds great !
Any chance something like this could be implemented in the near future ?
As discussed with Ohad, it would be nice if this feature would allow us to define on a puppetmaster node something like:
puppeteer::modules { "myenv1-mymodule1": env => "myenv1", module => "mysql", version => "0.1", }
- Category set to External Nodes
- Assignee set to Ohad Levy
- Target version set to 0.4
- Status changed from New to Closed
- % Done changed from 0 to 100
- Subject changed from Ability to add custom fields and options when editing a host. to Ability to add custom fields and options
Also available in: Atom
PDF