Skip to content

Conversation

@Sashwatdas123
Copy link
Contributor

@Sashwatdas123 Sashwatdas123 commented Nov 6, 2025

Details: We have added support for Ingest-Key changes to newrelic-lambda-cli integrations command

@codecov
Copy link

codecov bot commented Nov 6, 2025

Codecov Report

❌ Patch coverage is 94.11765% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 70.13%. Comparing base (6b5d8d4) to head (f38076a).

Files with missing lines Patch % Lines
newrelic_lambda_cli/cli/integrations.py 94.11% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #359      +/-   ##
==========================================
+ Coverage   69.86%   70.13%   +0.27%     
==========================================
  Files          20       20              
  Lines        1858     1882      +24     
==========================================
+ Hits         1298     1320      +22     
- Misses        560      562       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


if input.nr_api_key and input.nr_ingest_key:
raise click.UsageError(
"Please provide either the --nr-api-key or the --nr-ingest-key flag, but not both."

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sashwatdas123 It's not clear to me why this is invalid. I need to pass API key to set up account linking, but then it will choose an arbitrary license key. So passing both is perfectly valid.

To that end, maybe instead of this, it should allow specifying the ingest key name, and then the api key is used to find it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rittneje , Thank you for sharing this. We are looking into this and will update the PR.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants