Poor idempotency for NPM "secret" keys

[Infraded]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 5
• Ruby: 2.4 (Embedded)
• Distribution: CentOS 7
• Module version: Latest

How to reproduce (e.g Puppet code you use)

Use nodejs::npm::global_config_entry to declare any "secret" config key in NPM, such as _auth, _password, or registry_uri:_password

What are you seeing

Puppet is unable to retrieve the existing key due to protections in NPM that prevent it from showing any key that is prefixed with an _. This forces it to recreate the resource with every run, preventing a node from ever showing as unchanged.

What behaviour did you expect instead

Puppet should be able to verify the key already exists (outside of NPM commands) and is in the desired state without forcing it to be reset with every run

Output log

Any additional information you'd like to impart

PR incoming, looking for feedback on best method to check for these keys. Considering just testing for the value directly against the config, but different OSs have different paths to the global config file and this path is not currently known/managed in the module.