Age | Commit message (Collapse) | Author |
|
Based on a Stack Overflow question, it was noted that the documentation
for `file_line` isn't complete and the underlying behaviour somewhat
confusing.
https://stackoverflow.com/questions/46468922/how-to-change-the-contents-of-a-file-by-using-puppet/46473458
In this patch I add additional unit tests and better examples and
complete documentation.
|
|
I used the example code from this README file but i got downvotes from CI / jenkins / puppet-lint because it doesn't conform to Puppet style guides to use double quotes here. It produces "double quoted string containing no variables" warnings.
I wanted to fix the example locally but it was pointed out to me we should fix it upstream stdlib instead.
|
|
I rebased release on to master, so changes in master to the readme were not interpretted as changes on release in the payload sent to transifex. This commit should mark the README as modified in Transifex and hopefully they will be able to see the changes, e.g. to_json, to_yaml docs.
|
|
|
|
|
|
Add validate_domain_name function
|
|
(maint) move/rewrite round() as ruby function
|
|
|
|
add type for MAC address
|
|
|
|
Add new file_line option append_on_no_match
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Transifex, our translation service, only works with .md files, so this renames from .markdown to .md
|