-
Notifications
You must be signed in to change notification settings - Fork 2
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
Implement support for IPv6 endpoints #12
Conversation
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.
I'd like to see 100% unit test coverage of new lines added/modified please.
I think the matrix jobs need to be updated to have ipv6 support as well for the integration tests.
d71387e
to
55eb708
Compare
See my comment here: #10 (comment) |
fe3c5d5
to
8485fc0
Compare
Bumps juju@3.1 to pull a version that has support for IPv6. Bumps pytest-operator to avoid using a new version of juju with an old version of pytest-operator.
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.
Good work here! Just a couple of comments/suggestions.
Also, a note. If one of my review comment starts with [Nit]
, this means that the comment involves a preference of mine. Not a hard and fast rule 😅
Let me know if you have any questions!
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 👍
Edit: See your rebase. Thanks! 👍 |
87bf5ae
to
6bf1b97
Compare
This needed some refactoring on the current logic to verify that the host address is enclosed by square brackets, but it's nicer than using a big regex to try to validate at the same time IPv4, IPv6 and registered names.
Uses to mock the filesystem while creating and deleting the autofs files. Adds more tests to have 100% coverage on the manager module.
The most critical thing here is that we have to modify the settings from the lxd network to enable ipv6 addresses. This should probably be fine since we already modify the default LXD profile. Modifies CI to run integration tests using both IPv4 and IPv6.
Depends on #10.
Also removes our dependencies on regex. We expect this to not be a problem because we should also be validating the URL from the proxy or the relation interface.
Checklist