-
Notifications
You must be signed in to change notification settings - Fork 123
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
docs: add a how-to for setting open ports #1579
docs: add a how-to for setting open ports #1579
Conversation
The intention is this replaces the tutorial chapter.
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.
Looks good to me!
To verify that the correct ports are open in an integration test, deploy your | ||
charm as usual, and then try to connect to the appropriate ports. |
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.
Nice 😄 In this sense, integration tests are so much simpler...!
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've finished reviewing @tonyandrewmeyer, I think this is going to be a helpful new doc. Thanks!
Co-authored-by: Dave Wilding <tech@dpw.me>
Co-authored-by: Dave Wilding <tech@dpw.me>
Co-authored-by: Dave Wilding <tech@dpw.me>
Co-authored-by: Dave Wilding <tech@dpw.me>
Co-authored-by: Dave Wilding <tech@dpw.me>
Add a basic how-to guide that covers using
Unit.set_ports
to set which ports are open, and unit and integration tests for such.The intention is that this replaces the tutorial chapter (see #1511).