Closed findmyname666 closed 1 year 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.
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.
Any good soul who can take a look on this simple PR ?
Hey @findmyname666 , thank you!
Can you add a spec test to account for this new parameter?
Hi @findmyname666 - just hoping to check if there has been any progress on adding a spec test for this new functionality? Additionally, there are some conflicts that will need resolved before we can proceed. Thanks :-)
Hi @findmyname666! We are reviewing some of our ageing PRs, and as there has been no movement on this since August 16th, it's suggested that we close this request. If you have the time to pick this back up again in the near future and address the comments above - please do re-open this PR! (Or create a new one)
Thanks for all your work on this!
Hello all,
We are using custom APT transport for an internal mirror. However our transport is configurable via environment variables. In current state no ENV vars are available for update command. This PR introduce argument option
$::apt::update['environment']
to configure required ENV variables for APT update command.BR