plugin settings are confusing about foreman_expire_hosts HOT 6 CLOSED

:expired_on_input_field and :expired_on_field are to enable the field in the view. If this plugin is installed then by default the fields are shown, then we can remove these two fields.

:after: is also can remove and hardcode in overrides.

Actually this is one time edit so we kept in yaml file. If keeping these settings in settings objects, then will move. Please confirm so that i will work on it

from foreman_expire_hosts.

@nagarjuna I tend to think its best to put in it the db (we already support that - see other plugins for examples?)

thanks!

from foreman_expire_hosts.

@ohadlevy can i add Expiry Hosts subtab in settings and add all settings under that subtab?

from foreman_expire_hosts.

yes, this happens automatically when you have your own setting sub class

On Mon, May 11, 2015 at 3:07 PM, Nagarjuna Rachaneni <
[email protected]> wrote:

@ohadlevy https://github.com/ohadlevy can i add Expiry Hosts subtab in
settings and add all settings under that subtab?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

from foreman_expire_hosts.

@ohadlevy If i want to add setting default value as blank it is not supporting. example :notify_emails: must be string with coma(,) separated and default is blank. How can i do this ?

from foreman_expire_hosts.

Deprecated repo, see https://github.com/theforeman/foreman_expire_hosts

from foreman_expire_hosts.