Add TLS support for HTTP API endpoints #41
Merged
Conversation
This file contains 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
This was referenced Mar 22, 2023
leopaul36
reviewed
Mar 22, 2023
leopaul36
approved these changes
Mar 22, 2023
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.
Linked issues
avalanche_tracked_subnetsvariable toavalanchego_track_subnets#34Changes
avalanchego_https_enable. If set totrue, the user has to provide a certificate and a key for each node + the CA certificate. The CA certificate is added to the list of trusted certificates on all nodes to allow performing JSON RPC calls.avalanche_tracked_subnetstoavalanchego_track_subnetsto be closer to the config nameAdditional comments
Test these changes using:
Node Securitytutorial of Ash docs on the ansible-collection-tls-support branchansible-avalanche-getting-startedon the collection-tls-support branch