Azure functions overwite discover default service name #2321
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
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.
Hello team,
To fix the issue #2320 with the Service Name generated by the Azure Functions agent, i added a configuration
OverwriteDiscoverDefaultServiceNameitem to be able to overwrite or not the service name.So it will be possible to set the Service Name with the Artifact Name but also with the Azure Functions name.
To not break the compatibility with the previous release, this setting is set to
trueand the Azure Functions name is set by default.UnitTests and Documentation have been also updated.
Thank you for your approval.
Richard.