Loading...

XML

Word

Printable

Release Note Status:
None
Release Note Type:
None
Release Note Text:

Hide
Previously, there was no restriction on characters allowed in the subnet labels "name" configuration. For instance, it was possible to have text with spaces. This was however generating errors in the console plugin when trying to filter on it, as not all characters are allowed in filters. Additionally, clicking on the filter icon in the side panel for a subnet label did not work.
With this change, the configured subnet label name is validated immediately when configured in FlowCollector (allowing alpha-numeric characters and ":", "_" and "-"), and filtering on subnet labels from the console plugin now works as expected.

Show
Previously, there was no restriction on characters allowed in the subnet labels "name" configuration. For instance, it was possible to have text with spaces. This was however generating errors in the console plugin when trying to filter on it, as not all characters are allowed in filters. Additionally, clicking on the filter icon in the side panel for a subnet label did not work. With this change, the configured subnet label name is validated immediately when configured in FlowCollector (allowing alpha-numeric characters and ":", "_" and "-"), and filtering on subnet labels from the console plugin now works as expected.

From the UI, when trying to filter on a value that has a space, an error is returned:

"unauthorized sign in flows request"

A use case would be when defining a subnet label such as "AWS S3 us-east-1", and then filtering on it: it produces an error.

A simple workaround is to not use those forbidden characters when defining subnet labels.

Two options for fixing:

Either do a validation when creating a subnet label, with some forbidden characters matching the regex that is done on the console side (or stricter than that)
~~Or relax the rule on the console side, to allow any values.~~

(Edit: we're implementing the former: new regex validation rules on subnet label names)

Another issue is when clicking on the filter icon from the side-panel for a subnet label, nothing happens (there's an error in the JS console)

links to