chore: Add metadata action - step 1#1656
Merged
jcoscollanr merged 32 commits intomainfrom Mar 26, 2026
Merged
Conversation
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1656 +/- ##
==========================================
- Coverage 81.85% 81.78% -0.07%
==========================================
Files 214 214
Lines 25683 25683
Branches 4076 4076
==========================================
- Hits 21023 21006 -17
- Misses 3264 3277 +13
- Partials 1396 1400 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
… into mvick/add-metadata-action-step1
hmstepanek
requested changes
Feb 26, 2026
Contributor
hmstepanek
left a comment
There was a problem hiding this comment.
It looks like the license header check is failing. You just need to add the following license header to the top of each of these new files:
# Copyright 2010 New Relic, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
Also the megalinter step failed to commit I think you can run this locally via:
ruff format && ruff check --fix
You may need to pip install ruff first.
hmstepanek
approved these changes
Mar 24, 2026
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
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.

Overview
This PR adds the ability for the NR agent team to send agent metadata and binaries to New Relic for use in fleets and other features. This will be triggered normally during a release. but if it fails, it will not fail the release. It can also be run on-demand for backfilling older agent versions, to make corrections, or to re-run the job after a failure.
GH action info: https://github.com/newrelic/agent-metadata-action/blob/main/README.md
Testing
This PR is step 1 that will use a
TestAgentagent name instead ofNRPythonAgentThis PR needs to be merged to main in order to run the new on-demand workflow
A later PR will add a step in the release and use the real agent name