-
Notifications
You must be signed in to change notification settings - Fork 122
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
Fix IPv6 zone handling #66
Fix IPv6 zone handling #66
Conversation
Is there any way we can test IPv6 zones in integration tests? |
@WojciechowskiPiotr probably not in a sane way. I'm not sure which values are actually valid for it, and it probably depends on the system running the docker daemon, which at least in the dockerized tests we have no access to. |
Did you manage to manually test the patch? |
No. I only tested the regex itself. I'm hoping that @kristof-mattei could try it out. |
Patch looks fine, but let's test properly it before merging |
@WojciechowskiPiotr I'd love to test this, but any pointers how? |
@kristof-mattei you can use the way described here: https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#installing-a-collection-from-a-git-repository Here, it would be Alternatively (if you don't mind working with |
@kristof-mattei did you had a chance to test this yet? |
47f0daa
to
f4cbebd
Compare
I managed to test it for docker_container, it seems to work fine. I couldn't test it for docker_network (resp. Docker daemon always complained about an invalid CIDR), so I removed the change for that one. |
It looks like an arbitrary zone name works. If Docker daemon ever starts validating it (against what?) we either have to try to fix this test by a valid value, or remove it again.
488881a
to
d76b585
Compare
As Docker daemon seems to allow a random zone, we're able to (somewhat) test this in CI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@WojciechowskiPiotr @Andersson007 thanks for reviewing this! |
SUMMARY
Fixes #65. The same problem also appears in docker_network's CIDR validation. I don't know whether Docker supports zones here, but I don't see why we should restrict to non-zone CIDRs.
ISSUE TYPE
COMPONENT NAME
docker_container
docker_network