newrelic / newrelic/nr1-cloud-optimize

Cannot clone nerdpack in NR1?

Open
#152 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
53
Forks
34
Avg merge
15m
Merged PRs (30d)
1

Description

Description

I've been continuing to see an error when attempting to use the clone command within the repo:
› Error: Cannot destructure property 'path' of 'flags' as it is undefined.
› Code: UNKNOWN

This is from the command to clone the nerdpack:
nr1 nerdpack:clone -r https://github.com/newrelic/nr1-cloud-optimize.git

I've also confirmed NPM and Git are installed on the AWS Linux instance I'm using this on. I've also been able to create a basic nerdpack of my own without issue, so it appears to be something odd with the sync process

Steps to Reproduce

On a Linux EC2 instance running Amazon Linux, begin by SSH'ing into the instance and ensuring git/npm are installed. Once complete run the command and you will see the resulting error above.

Expected Behaviour

For it to clone the repository and allow deployment deployment.

Relevant Logs / Console output

See above

Your Environment

  • NR1 CLI version used: @datanerd/nr1/2.83.5 linux-x64 node-v16.11.1
  • Browser name and version: none
  • Operating System and version: AWS Linux 2

Additional context

I was able to clone the repo with git, but it still errors out complaining of various fields not existing. when attempting to serve it to the new relic environment.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing nr1 nerdpack:clone -r https://github.com/newrelic/nr1-cloud-optimize.git with NR1 CLI 2.83.5, Node 16.11.1, and Amazon Linux 2, then inspect the clone command's flag handling and sync flow. Done means the repository clones without the destructuring error and can be served for deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, javascript, node.js
Domain
cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.