Closed suchpuppet closed 3 years ago
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.
I'll need to update the spec tests to account for the new data type. I'll close and re-open whenever I have the time to do that.
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.
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.
Merging #953 (2e8b93f) into main (519f6d2) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #953 +/- ##
=======================================
Coverage 72.24% 72.24%
=======================================
Files 5 5
Lines 263 263
=======================================
Hits 190 190
Misses 73 73
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 8927af4...2e8b93f. Read the comment docs.
@suchpuppet This looks like a good change to me so I'm gonna go ahead and merge it. Thank you for putting the work in :)
This wraps the contents of the
/etc/apt/auth.conf
File resource as Sensitive so any credentials in that file are not exposed during report submissions or logged.With this small update, changing anything in the apt::auth_conf_entries parameter just looks like this instead of exposing credentials: