fix: backwards compatibility broken by #406, fixes #408 #409
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.
Signed-off-by: charles-knox-intel [email protected]
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When setting
ServerBindAddr
(newly introduced in #406), setting a blank value causesapp-functions-sdk-go
to default to theService.Host
value instead. This is actually not a backwards-compatible change.Issue Number: #408
What is the new behavior?
The new behavior is intended to actually be backwards-compatible this time. If
ServerBindAddr
is set to blank value, then the value that is sent toListenAndServe
is:<port>
. This is the previous behavior ofapp-functions-sdk-go
.Does this PR introduce a breaking change?
Are there any new imports or modules? If so, what are they used for and why?
No
Are there any specific instructions or things that should be known prior to reviewing?
No
Other information