New Relic Node.js agent code base. Developers are welcome to create pull requests here, please see our contributing guidelines. For New Relic technical support, please go to http://support.newrelic.com.
Apache License 2.0
967
stars
395
forks
source link
Add workflow for publishing Node Agent as an Azure site extension #2441
The Node Agent should be installable as an App Service Extension for Azure. In order to do this, we need to add a workflow for publishing an appropriately-formed bundle to NuGet. This requires effort in two areas:
Adding the necessary structure for the site extension to the agent codebase
Creating the Github Actions workflow to publish that bundle to NuGet (this issue)
Azure supports site extensions for Windows only, and the tools required to structure the extension appropriately are Windows-only. The workflow we create should use a Windows runner, and install the appropriate .NET tooling to create the extension. We can use the Java Agent's site extension approach as a reference for determining how to build the properly structured bundle.
The GitHub Actions workflow for Node will
install the necessary .NET/NuGet tooling to build the site extension bundle
build the site extension to include the latest New Relic Node agent
publish to NuGet with a version matching that of the agent
Acceptance Criteria
As an Azure user, I expect to be able to install the Node agent as an App Service Extension.
Design Consideration/Limitations
Azure site extensions support only Windows.
Site extensions run their install script when the application they're part of restarts, so we want the install script to take as little time as possible to complete.
workato-integration[bot]
commented
1 month ago
Description
The Node Agent should be installable as an App Service Extension for Azure. In order to do this, we need to add a workflow for publishing an appropriately-formed bundle to NuGet. This requires effort in two areas:
Azure supports site extensions for Windows only, and the tools required to structure the extension appropriately are Windows-only. The workflow we create should use a Windows runner, and install the appropriate .NET tooling to create the extension. We can use the Java Agent's site extension approach as a reference for determining how to build the properly structured bundle.
The GitHub Actions workflow for Node will
Acceptance Criteria
As an Azure user, I expect to be able to install the Node agent as an App Service Extension.
Design Consideration/Limitations
Azure site extensions support only Windows. Site extensions run their install script when the application they're part of restarts, so we want the install script to take as little time as possible to complete.