Bug 1414036

Summary: [RFE] npm plugin should collect npm configuration
Product: Red Hat Enterprise Linux 6 Reporter: Miroslav Hradílek <mhradile>
Component: sosAssignee: Shane Bradley <sbradley>
Status: CLOSED WONTFIX QA Contact: Miroslav Hradílek <mhradile>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9CC: agk, bmr, gavin, plambri, pmoravec, sbradley
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1414035 Environment:
Last Closed: 2017-05-10 13:59:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1414035    
Bug Blocks:    

Description Miroslav Hradílek 2017-01-17 15:14:08 UTC
RHEL-6 does not contain this either

+++ This bug was initially created as a clone of Bug #1414035 +++

Description of problem:
Currently npm plugin does not collect npm configuration and npmrc files. It would be useful to know how npm is configured globally and what user and project specific modifications were taken.

For example whether user is using different registry would be good to know.

I believe collecting output of this command "npm config list -l" would suffice.

Version-Release number of selected component (if applicable):

Actual results:
No npm configuration information is collected.

Expected results:
Output of "npm config list -l" is collected.

Additional info:
It should call the command when project is specified to pick up project specific changes made in project npmrc or package.json.

Comment 5 Shane Bradley 2017-05-10 13:59:56 UTC
I am closing this bugzilla as RHEL 6.10 is in production phase 3 and no new plugins will be added to sos. For more information see the following link:

- Red Hat Enterprise Linux Life Cycle