Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Custom Fields can't be used in a filter

#400

Since 1.3 you are able to generate custom fields on the fly based on the input from your resource provider. These fields are shown in the UI but are not usable to create a filter.
According to Alex-SF (via IRC) this is an oversight and should be implemented.

Reported by Marcello de Sousa · July 22nd, 2011 @ 07:45 AM

State: new
Milestone: none
Assigned to: nobody

Activity

  1. Alex-SF
    Alex-SF

    Some custom fields might also be a list (like tags). Perhaps Rundeck can interpret them if they are unquoted lists. Eg in yaml form,

    • this is a list:
      • classes: apache,nginix
    • this is a string:
      • classes: "apache,nginix"

    Allowing a custom field to be interpreted as a list will facilitate tags-like filtering. Eg

    • Include nodes that have a class of either apache or nginix
      • `` -I classes=apache,nginx
    • Include nodes that have a class nginix and a role web
      • -I classes=nginix -I role=web

    July 22nd, 2011 @ 08:12 AM

  2. Greg Schueler
    Greg Schueler

    The GUI simply doesn't support filtering by custom attributes yet. This is
    supported in the underlying filter code, and the CLI tools. it needs to be
    added to the GUI

    February 16th, 2012 @ 04:13 PM

  3. Greg Schueler
    Greg Schueler

    Yes, needs to be supported in the xml/yaml serialization formats as well too

    February 16th, 2012 @ 05:44 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.