Project

General

Profile

Actions

Bug #8628

closed

'ip' fields in techniques/directives does not support ipv6

Added by Janos Mattyasovszky over 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
2
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Hi,

Currently there is an "ip" type of contraint for the input fields in the metadata.xml, however, there is none for the IPv6 Address format.

Since IPv6 is getting used more and more, it would be highly recommended to have a validated type that accepts ipv6 formats.

EDIT: the implemented solution have three constraints:

 <CONSTRAINT><TYPE>ip</TYPE></CONSTRAINT>    <!-- accept both ipv4 and ipv6 -->
 <CONSTRAINT><TYPE>ipv4</TYPE></CONSTRAINT>  <!-- accept ipv4 only -->
 <CONSTRAINT><TYPE>ipv6</TYPE></CONSTRAINT>  <!-- accept ipv6 only -->

Subtasks 1 (0 open1 closed)

Bug #11217: Ipv6 constraint NOT PORTED to Rudder 4.0 and upReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF