You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our scenario some nodes must be excluded based on tags from job execution.
In the Rundeck UI it works with tags:filter1+filter2 !tags:filter3
When I try the same with the rd cli run -i <job id> -F 'tags:filter1+filter2 !tags:filter3' command it does not respect the negative selection and ignore the complete filter and run the command on all nodes.
In tests with rd nodes list -p project -F 'tags:filter1+filter2 !tags:filter3' the correct set of nodes was returned.
Is there anything wrong in my rd run command?
Thanks,
Torben
The text was updated successfully, but these errors were encountered:
I wonder if there's an issue with escaping the ! character. The code for rd nodes list does not appear to use the exact same methods to send filters to Rundeck as rd run does in 2.0.8, but I could be reading it incorrectly. @tehret77@koraz0815 did either of you try sending in filters directly via the API instead of rd command?
Hello,
In our scenario some nodes must be excluded based on tags from job execution.
In the Rundeck UI it works with
tags:filter1+filter2 !tags:filter3
When I try the same with the rd cli
run -i <job id> -F 'tags:filter1+filter2 !tags:filter3'
command it does not respect the negative selection and ignore the complete filter and run the command on all nodes.In tests with
rd nodes list -p project -F 'tags:filter1+filter2 !tags:filter3'
the correct set of nodes was returned.Is there anything wrong in my
rd run
command?Thanks,
Torben
The text was updated successfully, but these errors were encountered: