Project

General

Profile

Actions
Copy link

User story #3622

closed

User story #3613: Add possibility to create a group with a combinaison of matching a regex and not matching another regex

Add a "not matching rexex" filter comparator for node search

Added by François ARMAND almost 11 years ago. Updated over 8 years ago.

Status:
Released
Priority:
1
Assignee:
François ARMAND
Category:
Web - Nodes & inventories
Target version:
2.6.3
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

For searching node (groups, etc), we would like to have a comparator "not matching that regex", so that we could express condition like "nodes matching that range of IP and not matching that other range"

Actions
Copy link
 #1

Updated by François ARMAND almost 11 years ago

  • Status changed from 8 to 10
  • Pull Request set to https://github.com/Normation/rudder/pull/223

There is an implementation of the solution, took 30min to implements.

Actions
Copy link
 #2

Updated by François ARMAND almost 11 years ago

  • Assignee changed from François ARMAND to Jonathan CLARKE
Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 11 years ago

Looks great to me (from a TR point of view) !

Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from 10 to Pending technical review
Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from Pending technical review to 12
Actions
Copy link
 #6

Updated by François ARMAND almost 11 years ago

  • Status changed from 12 to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Nicolas PERRON almost 11 years ago

Actions
Copy link
 #8

Updated by Nicolas CHARLES almost 11 years ago

  • Target version changed from 2.7.0~beta1 to 2.6.3

Hum, the code has been done on the 2.6 branch, so I'm retargeting it to 2.6.3

Actions
Copy link
 #9

Updated by François ARMAND almost 11 years ago

  • Status changed from Pending release to Discussion
  • Assignee changed from Jonathan CLARKE to François ARMAND
  • Priority changed from 3 to 1

This feature was incorrectly merged in Rudder 2.6.
We are going to revert it and merge it back in Rudder 2.7.

Actions
Copy link
 #10

Updated by François ARMAND almost 11 years ago

  • Status changed from Discussion to 12
Actions
Copy link
 #11

Updated by François ARMAND almost 11 years ago

  • Status changed from 12 to Pending release
Actions
Copy link
 #13

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.3 to 2.7.0~rc1
Actions
Copy link
 #14

Updated by Nicolas PERRON over 10 years ago

It was done for Rudder 2.7.0~beta1... I have to add it to the changelog

Actions
Copy link
 #15

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.7.0~rc1 to 2.7.0~beta1
Actions
Copy link
 #16

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released
Actions
Copy link
 #17

Updated by Benoît PECCATTE about 9 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link
 #18

Updated by Benoît PECCATTE over 8 years ago

  • Target version changed from 2.7.0~beta1 to 2.6.3
Actions
Copy link

Also available in: Atom PDF