Age | Commit message (Collapse) | Author |
|
(maint) Stdlib::Compat::Integer accepts numbers with newlines apparently
|
|
(MODULES-5113) Make line support Sensitive
|
|
(MODULES-5186) - do not run file_line unit tests on windows.
|
|
|
|
|
|
|
|
This reverts commit 409a974095a3f5b637e091494b5d14b451c5de78.
After thinking about this, use case, and function naming, I think it's
probably best for now to keep things simple and let `fact()` be
single-purpose for looking up facts with no potentially confusing
extensions. The only use case where the name makes sense is where it's
being used on the `$facts` hash, and I think we'd rather in that
circumstance promote the raw use of `fact()`.
|
|
|
|
Fix headers in CHANGELOG.md so that headers render correctly
|
|
Because sometimes people want to use an alternative data set, but treat
it like it's a set of facts.
|
|
The fact() function allows dot-notation reference to facts. It is an
alternative to using $facts directly with array-indexing. Array-indexing
is often onerous to use since it doesn't align with how structured facts
are accessed elsewhere in the ecosystem and if any element in a
multi-step path doesn't exist, array indexing can cause a compilation
failure.
Example usage:
fact('os.family')
|
|
Do this by making it a property. The idea is to get rid of the warning
that appears when a Sensitive value is passed to the line attribute.
|
|
(MODULES-5144) Prep for puppet 5
|
|
|
|
|
|
4.17.1 Release Mergeback
|
|
Release prep for 4.17.1
|
|
|
|
(MODULES-5095) Workaround for PUP-7650
|
|
This commit adds a simple workaround for the problem described in
PUP-7650. The workaround is harmless and can remain in place regardless
of if the fix for PUP-7650 is in place or not.
|
|
MODULES-4821 puppetlabs-stdlib: Update the version compatibility to >= 4.7.0 < 5.0.0
|
|
(FM-6197) formatting fixes for file_line resource
|
|
|
|
< 5.0.0
|
|
Merge back 4.17.0
|
|
|
|
```
file { '/tmp/somefile':
ensure => 'file',
}
File['/tmp/somefile'] -> Package <| |>
ensure_packages($somearray)
```
If $somearray is undefined or one of the elements contains an empty
string, an error like the following is thrown:
Could not find resource 'Package[]' for relationship from
'File[/tmp/somefile]' on node $::fqdn
|
|
|
|
|
|
|
|
defined_with_params() now returns false for defined types, causing
duplicate resources when using ensure_resources().
Introduced by 4f19c27 in PE-20308.
|
|
Transifex, our translation service, only works with .md files, so this renames from .markdown to .md
|
|
(MODULES-4706) prerelease fixes
|
|
|
|
|
|
Removing italics for 'undef' value
|
|
This causes issues with displaying a Japanese translation. It struggles
rendering the `) therefore removing italics.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(PE-20308) Correct boundary for 4.5 vs 4.6
|
|
|
|
(PE-20308) Pass a literal type and not a string to findresource
|
|
- `defined_with_params` calls `findresource(reference.to_s)`
- `findresource` is
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/parser/compiler.rb#L407
and points to
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/resource/catalog.rb#L352
- This calls `Puppet::Resource.new` with the type
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/resource/catalog.rb#L366
- This ends up calling `resource_type` via
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/resource.rb#L317-L319
and that ends up declaring the type via the autoloader api at
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/resource.rb#L390
- But why does the autoloader API fail to find it in the current
environment?
- Okay, so when the autoloader is trying to find the type, it uses the
typeloader to look it up in the current environment
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/metatype/manager.rb#L171
- this calls `get_file` and `mark_loaded`
https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/util/autoload.rb#L64-L67
Suggested workaround is to pass a literal type instead of a string to
`findresource` to fix in stdlib, and also to fix loading/requiring of
type in core puppet.
This seems to affect more recent versions of puppet, so fallback to
original behavior on pre-4.5
|
|
Release mergeback
|
|
Ruby 1.8 doesn't support open_args
|