fix: consolidate callbackAddress and hostname#1447
Merged
Conversation
carlos-schmidt
changed the title
|
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
2 participants
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.
Consolidates
CoreConfig.callbackAddressandHttpEndpointConfig.hostnameintoHttpEndpointConfig.hostname.HttpEndpointConfig.hostnameis now used for defining the external URL of the FA³ST Service for theHttpEndpoint. It defaults to the local hostname/ip address determined by JVM.If
hostnameis defined, no additional scheme or port will be added.If multiple
HttpEndpointsare defined,MessageBusCloudEventsuses one of them for aCloudEvent's source URI. Non-localhostnames take precedence (i.e., notlocalhost,127.0.0.1, etc.).This info can also be found in the docs.