-
Notifications
You must be signed in to change notification settings - Fork 145
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
task to check if puppet resources have a spec described #439
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #439 +/- ##
==========================================
- Coverage 41.71% 40.85% -0.86%
==========================================
Files 10 10
Lines 676 700 +24
==========================================
+ Hits 282 286 +4
- Misses 394 414 +20 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea, but I don't want to test my private classes (like $module::params
). Sadly you can only declare a class as private using puppet-strings so that may be hard with your existing code.
Overall puppet-strings can already parse and extract the various types, which is probably better than using regular expressions. Any thoughts on using puppet-strings to generate a list of all resources?
Thanks for the feedback. I'll check it out, cheers! |
I like this and share the same opinion as @ekohl . I think this would be a helpful addition to puppetlabs_spec_helper. |
Anyone interested in this?
Request for comment / improvements / toss it out?
Example: