Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure NPM secret keys are idempotent in global_config_entry #386

Merged
merged 3 commits into from
Jan 31, 2019

Conversation

jplindquist
Copy link
Contributor

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Fixes #326

@bastelfreak bastelfreak added bug Something isn't working needs-work not ready to merge just yet labels Jan 31, 2019
@bastelfreak bastelfreak removed the needs-work not ready to merge just yet label Jan 31, 2019
@bastelfreak
Copy link
Member

Thanks!

@bastelfreak bastelfreak merged commit 1cc48f1 into voxpupuli:master Jan 31, 2019
aboks added a commit to aboks/puppet-nodejs that referenced this pull request Mar 1, 2019
The fix in voxpupuli#386 fixes
idempotence for secrets that contain characters (like '=') that cause
NPM to quote them in npmrc. Secrets that end up unquoted in npmrc are
not handled correctly however. This fix makes the quotes optional when
checking if the config value is already set correctly.
juniorsysadmin pushed a commit that referenced this pull request Apr 9, 2019
* Fix idempotence of unquoted secrets

The fix in #386 fixes
idempotence for secrets that contain characters (like '=') that cause
NPM to quote them in npmrc. Secrets that end up unquoted in npmrc are
not handled correctly however. This fix makes the quotes optional when
checking if the config value is already set correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Poor idempotency for NPM "secret" keys
3 participants