-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to input ipv6 where it makes sense #70
Allow users to input ipv6 where it makes sense #70
Conversation
It feels like this will probably come close to solving https://bugzilla.redhat.com/show_bug.cgi?id=1212896 Do you want to take that @isimluk? |
When users inputs static IPv4 we should assert it is valid IPv4. All other inputs shall allow for IPv6 as well. This commit does not allow IPv6 yet, it just makes the logical distinction.
Sure, taking, working on it anyway. It will get fixed in one of the following prs. |
We will need new prompt for static ipv6 as things are different and people may want to have both. |
Checked commits https://github.com/isimluk/manageiq-gems-pending/compare/ee3769eac683f1bd878077a344b58b248db52dfd~...4f7202e22037c29565111a92d2152876841c4c65 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Getting this into the build early will make my job easier, when I will try to set-up multi region, multi-zone over ipv6. Thanks! |
Thanks!! |
What
In many prompts we allow users to put IP address. In some prompts it makes sense to only accept IPv4 addresses (when setting up static IPv4). In other cases it makes sense to accept IPv4 or IPv6.
This PR makes
Test Network Configuration
to magically work with IPv6.I'll continue to work with other dialogs to make sure, we are able to process IPv6. However, we can allow IPv6 inputs to be valid now.