chore: Update Azure Site Extension to include support for Azure Functions #2976
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2976 +/- ##
=======================================
Coverage 82.16% 82.16%
=======================================
Files 473 473
Lines 30364 30364
Branches 3388 3388
=======================================
Hits 24948 24948
Misses 4617 4617
Partials 799 799
Flags with carried forward coverage won't be shown. Click here to find out more. |
chynesNR
approved these changes
Jan 31, 2025
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.
Update the Azure Websites Site Extension Nuget package to detect when it's being added to an Azure Function.
If the
FUNCTIONS_WORKER_RUNTIMEenvironment variable is detected, the extension addsNEW_RELIC_AZURE_FUNCTION_MODE_ENABLED=1andNEW_RELIC_LOG_DIRECTORY=%HOME%\LogFiles\NewRelictoapplicationHost.xdt.With this change, the customer only needs to add the
NEW_RELIC_LICENSE_KEYenvironment variable manually and the agent will "just work" in an Azure function. TheNEW_RELIC_AGENT_VERSION_OVERRIDEenvironment variable is supported as usual.