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

Add support for mocking (Onceover/rspec) #70

Merged
merged 1 commit into from
Oct 25, 2021

Conversation

alexjfisher
Copy link
Contributor

Document how to mock node_encrypt with Onceover and add the explicit
support necessary in the legacy node_encrypted_file type.

Document how to mock `node_encrypt` with `Onceover` and add the explicit
support necessary in the legacy `node_encrypted_file` type.
@puppet-community-rangefinder
Copy link

node_encrypted_file is a type

Breaking changes to this file MAY impact these 1 modules (near match):

This module is declared in 1 of 575 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@binford2k binford2k merged commit be30e98 into puppetlabs:master Oct 25, 2021
binford2k added a commit that referenced this pull request Oct 26, 2021
This should not have been committed. Alex solved it in a different way
in #70.
@alexjfisher
Copy link
Contributor Author

At the time, I had no Puppet 6 so was only using the legacy type. I'll submit a follow up PR also needed if using node_encrypt.secret().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants