Closed sheenaajay closed 4 years ago
that may have no external impact to Forge modules.
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.
:exclamation: No coverage uploaded for pull request base (
main@2e794c9
). Click here to learn what that means. The diff coverage isn/a
.
@@ Coverage Diff @@
## main #948 +/- ##
=======================================
Coverage ? 71.86%
=======================================
Files ? 5
Lines ? 263
Branches ? 0
=======================================
Hits ? 189
Misses ? 74
Partials ? 0
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 2e794c9...46298a0. Read the comment docs.
Request for a review This PR addressed the ticket https://tickets.puppetlabs.com/browse/MODULES-10804 Added changes for both behaviour by adding new parameter
sources_list_force
for force purge.By default its set to false. Added unit tests to verify the changes. As of now the unit tests are failing on apt module on main branch, A ticket is opened for the failures. https://tickets.puppetlabs.com/browse/IAC-1143 Added temporary workaround as mentioned in the above ticket. Submitting the changes for review since the unit tests failures are not from this PR. Attaching the release check from both puppet agent 5 and puppet agent 6