docs: add required ports information for cloud connections#3194
Merged
reubenmiller merged 1 commit intothin-edge:mainfrom Oct 21, 2024
Merged
docs: add required ports information for cloud connections#3194reubenmiller merged 1 commit intothin-edge:mainfrom
reubenmiller merged 1 commit intothin-edge:mainfrom
Conversation
Signed-off-by: Reuben Miller <reuben.d.miller@gmail.com>
61bf5c5 to
6def37a
Compare
Contributor
Robot Results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Add information about which ports are required by thin-edge.io to communicate to each cloud.
This work was spawned from a debug session which a customer which was using thin-edge.io behind a strictly controlled network and firewall rules needed to be created before thin-edge.io could connect to the appropriate cloud.
An additional "Debug section" could also be added, however it was decided it would be a better UX to create built-in command to do the connectivity checks like "can I reach the network" to give clear guidance on how to check these scenearios.
Types of changes
Paste Link to the issue
Checklist
cargo fmtas mentioned in CODING_GUIDELINEScargo clippyas mentioned in CODING_GUIDELINESFurther comments