Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x
- Puppet >= 7.0.0 < 9.0.0
- , , , , , , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-inifile', '6.1.1'Learn more about managing modules with a PuppetfileDocumentation
inifile
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with inifile module
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- License
- Development - Guide for contributing to the module
Overview
The inifile module lets Puppet manage settings stored in INI-style configuration files.
Module Description
Many applications use INI-style configuration files to store their settings. This module supplies two custom resource types to let you manage those settings through Puppet.
Setup
Beginning with inifile
To manage a single setting in an INI file, add the ini_setting type to a class:
ini_setting { "sample setting":
ensure => present,
path => '/tmp/foo.ini',
section => 'bar',
setting => 'baz',
value => 'quux',
}
Usage
The inifile module is used to:
- Support comments starting with either '#' or ';'.
- Support either whitespace or no whitespace around '='.
- Add any missing sections to the INI file.
It does not manipulate your file any more than it needs to. In most cases, it doesn't affect the original whitespace, comments, or ordering. See the common usages below for examples.
Manage multiple values in a setting
Use the ini_subsetting type:
ini_subsetting {'sample subsetting':
ensure => present,
section => '',
key_val_separator => '=',
path => '/etc/default/pe-puppetdb',
setting => 'JAVA_ARGS',
subsetting => '-Xmx',
value => '512m',
}
Results in managing this -Xmx subsetting:
JAVA_ARGS="-Xmx512m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/pe-puppetdb/puppetdb-oom.hprof"
Use a non-standard section header
ini_setting { 'default minage':
ensure => present,
path => '/etc/security/users',
section => 'default',
setting => 'minage',
value => '1',
section_prefix => '',
section_suffix => ':',
}
Results in:
default:
minage = 1
Use a non-standard indent character
To use a non-standard indent character or string for added settings, set the indent_char and the indent_width parameters. The indent_width parameter controls how many indent_char appear in the indent.
ini_setting { 'procedure cache size':
ensure => present,
path => '/var/lib/ase/config/ASE-16_0/SYBASE.cfg',
section => 'SQL Server Administration',
setting => 'procedure cache size',
value => '15000',
indent_char => "\t",
indent_width => 2,
}
Results in:
[SQL Server Administration]
procedure cache size = 15000
Implement child providers
You might want to create child providers that inherit the ini_setting provider for one of the following reasons:
- To make a custom resource to manage an application that stores its settings in INI files, without recreating the code to manage the files themselves.
- To purge all unmanaged settings from a managed INI file.
To implement child providers, first specify a custom type. Have it implement a namevar called name and a property called value:
#my_module/lib/puppet/type/glance_api_config.rb
Puppet::Type.newtype(:glance_api_config) do
ensurable
newparam(:name, :namevar => true) do
desc 'Section/setting name to manage from glance-api.conf'
# namevar should be of the form section/setting
newvalues(/\S+\/\S+/)
end
newproperty(:value) do
desc 'The value of the setting to define'
munge do |v|
v.to_s.strip
end
end
end
Your type also needs a provider that uses the ini_setting provider as its parent:
# my_module/lib/puppet/provider/glance_api_config/ini_setting.rb
Puppet::Type.type(:glance_api_config).provide(
:ini_setting,
# set ini_setting as the parent provider
:parent => Puppet::Type.type(:ini_setting).provider(:ruby)
) do
# implement section as the first part of the namevar
def section
resource[:name].split('/', 2).first
end
def setting
# implement setting as the second part of the namevar
resource[:name].split('/', 2).last
end
# hard code the file path (this allows purging)
def self.file_path
'/etc/glance/glance-api.conf'
end
end
Now you can manage the settings in the /etc/glance/glance-api.conf file as individual resources:
glance_api_config { 'HEADER/important_config':
value => 'secret_value',
}
If you've implemented self.file_path, you can have Puppet purge the file of the all lines that aren't implemented as Puppet resources:
resources { 'glance_api_config':
purge => true,
}
Manage multiple ini_settings
To manage multiple ini_settings, use the inifile::create_ini_settings function.
$defaults = { 'path' => '/tmp/foo.ini' }
$example = { 'section1' => { 'setting1' => 'value1' } }
inifile::create_ini_settings($example, $defaults)
Results in:
ini_setting { '[section1] setting1':
ensure => present,
section => 'section1',
setting => 'setting1',
value => 'value1',
path => '/tmp/foo.ini',
}
To include special parameters, use the following code:
$defaults = { 'path' => '/tmp/foo.ini' }
$example = {
'section1' => {
'setting1' => 'value1',
'settings2' => {
'ensure' => 'absent'
}
}
}
inifile::create_ini_settings($example, $defaults)
Results in:
ini_setting { '[section1] setting1':
ensure => present,
section => 'section1',
setting => 'setting1',
value => 'value1',
path => '/tmp/foo.ini',
}
ini_setting { '[section1] setting2':
ensure => absent,
section => 'section1',
setting => 'setting2',
path => '/tmp/foo.ini',
}
Manage multiple ini_settings with Hiera
For the profile example:
class profile::example (
Hash $settings,
) {
$defaults = { 'path' => '/tmp/foo.ini' }
inifile::create_ini_settings($settings, $defaults)
}
Provide this in your Hiera data:
profile::example::settings:
section1:
setting1: value1
setting2: value2
setting3:
ensure: absent
Results in:
ini_setting { '[section1] setting1':
ensure => present,
section => 'section1',
setting => 'setting1',
value => 'value1',
path => '/tmp/foo.ini',
}
ini_setting { '[section1] setting2':
ensure => present,
section => 'section1',
setting => 'setting2',
value => 'value2',
path => '/tmp/foo.ini',
}
ini_setting { '[section1] setting3':
ensure => absent,
section => 'section1',
setting => 'setting3',
path => '/tmp/foo.ini',
}
Reference
See REFERENCE.md
Limitations
Supported operating systems
For an extensive list of supported operating systems, see metadata.json
create_ini_settings
When using inifile::create_ini_settings it’s worth noting that namespace tags will not be applied to the resource. If you need these namespace tags we advise using the standard ini_setting resource.
For more information about resource tags, please see this article.
License
This codebase is licensed under the Apache2.0 licensing, however due to the nature of the codebase the open source dependencies may also use a combination of AGPL, BSD-2, BSD-3, GPL2.0, LGPL, MIT and MPL Licensing.
Development
We are experimenting with a new tool for running acceptance tests. It's name is puppet_litmus this replaces beaker as the test runner. To run the acceptance tests follow the instructions here.
Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.
We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
For more information, see our module contribution guide.
Contributors
To see who's already involved, see the list of contributors.
Reference
Table of Contents
Resource types
ini_setting: ini_settings is used to manage a single setting in an INI fileini_subsetting: ini_subsettings is used to manage multiple values in a setting in an INI file
Functions
create_ini_settings: DEPRECATED. Use the namespaced functioninifile::create_ini_settingsinstead.inifile::create_ini_settings: This function is used to create a set of ini_setting resources from a hash
Resource types
ini_setting
ini_settings is used to manage a single setting in an INI file
Properties
The following properties are available in the ini_setting type.
ensure
Valid values: present, absent
Ensurable method handles modeling creation. It creates an ensure property
Default value: present
value
The value of the setting to be defined.
Parameters
The following parameters are available in the ini_setting type.
force_new_section_creationindent_charindent_widthkey_val_separatornamepathproviderrefreshonlysectionsection_prefixsection_suffixsettingshow_diff
force_new_section_creation
Valid values: true, false, yes, no
Create setting only if the section exists
Default value: true
indent_char
The character to indent new settings with.
Default value:
indent_width
The number of indent_chars to use to indent a new setting.
key_val_separator
The separator string to use between each setting name and value.
Default value: =
name
namevar
An arbitrary name used as the identity of the resource.
path
The ini file Puppet will ensure contains the specified setting.
provider
The specific backend to use for this ini_setting resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
refreshonly
Valid values: true, false, yes, no
A flag indicating whether or not the ini_setting should be updated only when called as part of a refresh event
Default value: false
section
The name of the section in the ini file in which the setting should be defined.
Default value: ''
section_prefix
The prefix to the section name\'s header.
Default value: [
section_suffix
The suffix to the section name\'s header.
Default value: ]
setting
The name of the setting to be defined.
show_diff
Valid values: true, md5, false
Whether to display differences when the setting changes.
Default value: true
ini_subsetting
ini_subsettings is used to manage multiple values in a setting in an INI file
Properties
The following properties are available in the ini_subsetting type.
ensure
Valid values: present, absent
Ensurable method handles modeling creation. It creates an ensure property
Default value: present
value
The value of the subsetting to be defined.
Parameters
The following parameters are available in the ini_subsetting type.
delete_if_emptyinsert_typeinsert_valuekey_val_separatornamepathproviderquote_charsectionsettingshow_diffsubsettingsubsetting_key_val_separatorsubsetting_separatoruse_exact_match
delete_if_empty
Valid values: true, false
Set to true to delete the parent setting when the subsetting is empty instead of writing an empty string
Default value: false
insert_type
Valid values: start, end, before, after, index
Where the new subsetting item should be inserted
- :start - insert at the beginning of the line.
- :end - insert at the end of the line (default).
- :before - insert before the specified element if possible.
- :after - insert after the specified element if possible.
- :index - insert at the specified index number.
Default value: end
insert_value
The value for the insert types which require one.
key_val_separator
The separator string to use between each setting name and value.
Default value: =
name
namevar
An arbitrary name used as the identity of the resource.
path
The ini file Puppet will ensure contains the specified setting.
provider
The specific backend to use for this ini_subsetting resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
quote_char
The character used to quote the entire value of the setting. Valid values are '', '\"' and \"'\"
Default value: ''
section
The name of the section in the ini file in which the setting should be defined.
Default value: ''
setting
The name of the setting to be defined.
show_diff
Valid values: true, md5, false
Whether to display differences when the setting changes.
Default value: true
subsetting
The name of the subsetting to be defined.
subsetting_key_val_separator
The separator string between the subsetting name and its value. Defaults to the empty string.
Default value: ''
subsetting_separator
The separator string between subsettings. Defaults to the empty string.
Default value:
use_exact_match
Valid values: true, false
Set to true if your subsettings don\'t have values and you want to use exact matches to determine if the subsetting exists.
Default value: false
Functions
create_ini_settings
Type: Ruby 4.x API
DEPRECATED. Use the namespaced function inifile::create_ini_settings instead.
create_ini_settings(Any *$args)
The create_ini_settings function.
Returns: Any
*args
Data type: Any
inifile::create_ini_settings
Type: Ruby 4.x API
This function is used to create a set of ini_setting resources from a hash
inifile::create_ini_settings(Hash $settings, Optional[Hash] $defaults)
The inifile::create_ini_settings function.
Returns: Any
settings
Data type: Hash
A hash of settings you want to create ini_setting resources from
defaults
Data type: Optional[Hash]
A hash of defaults you would like to use in the ini_setting resources
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
v6.1.1 - 2024-03-11
Fixed
v6.1.0 - 2023-06-20
Added
Other
v6.0.0 - 2023-04-11
Changed
- (CONT-783) - Add puppet 8 support/Drop puppet 6 support #505 (jordanbreen28)
v5.4.1 - 2023-04-06
Fixed
- pdksync - (CONT-189) Remove support for RedHat6 / OracleLinux6 / Scientific6 #492 (david22swan)
- pdksync - (CONT-130) - Dropping Support for Debian 9 #489 (jordanbreen28)
v5.4.0 - 2022-10-03
Added
- pdksync - (GH-cat-11) Certify Support for Ubuntu 22.04 #484 (david22swan)
- pdksync - (GH-cat-12) Add Support for Redhat 9 #480 (david22swan)
Fixed
- (MAINT) Drop support for Solaris 10, Windows Server 2008 R2, and AIX 5.3 and 6.1 #485 (jordanbreen28)
- Fix broken idempotency with empty sections #483 (kajinamit)
v5.3.0 - 2022-05-23
Added
- pdksync - (FM-8922) - Add Support for Windows 2022 #468 (david22swan)
- pdksync - (IAC-1753) - Add Support for AlmaLinux 8 #463 (david22swan)
- pdksync - (IAC-1751) - Add Support for Rocky 8 #462 (david22swan)
- match section names containing prefix character (normally [) #457 (tja523)
Fixed
- pdksync - (GH-iac-334) Remove Support for Ubuntu 14.04/16.04 #471 (david22swan)
- pdksync - (IAC-1787) Remove Support for CentOS 6 #466 (david22swan)
- pdksync - (IAC-1598) - Remove Support for Debian 8 #461 (david22swan)
v5.2.0 - 2021-08-26
Added
- pdksync - (IAC-1709) - Add Support for Debian 11 #458 (david22swan)
Fixed
- (IAC-1741) Allow stdlib v8.0.0 #459 (david22swan)
v5.1.0 - 2021-06-28
Added
v5.0.1 - 2021-03-29
Fixed
- (IAC-149) - Removal of Unsupported Translate Module #442 (david22swan)
v5.0.0 - 2021-03-03
Changed
- pdksync - Remove Puppet 5 from testing and bump minimal version to 6.0.0 #432 (carabasdaniel)
v4.4.0 - 2020-12-08
Added
- (feat) - Add Puppet 7 support #422 (daianamezdrea)
v4.3.1 - 2020-11-09
Fixed
- (IAC-992) - Removal of inappropriate terminology #415 (david22swan)
v4.3.0 - 2020-09-10
Added
- pdksync - (IAC-973) - Update travis/appveyor to run on new default branch
main#407 (david22swan) - Add delete_if_empty parameter to the ini_subsetting type/provider #405 (mmarod)
- (IAC-746) - Add ubuntu 20.04 support #396 (david22swan)
v4.2.0 - 2020-04-27
Added
- Finish API conversion of
create_ini_settings#387 (alexjfisher)
v4.1.0 - 2020-01-15
Added
- pdksync - (FM-8581) - Debian 10 added to travis and provision file refactored #374 (david22swan)
- Puppet 4 functions #373 (binford2k)
- pdksync - "MODULES-10242 Add ubuntu14 support back to the modules" #368 (sheenaajay)
- (FM-8689) - Addition of Support for CentOS 8 #366 (david22swan)
v4.0.0 - 2019-11-11
Changed
Added
v3.1.0 - 2019-08-01
Added
- FM-8222 - Port Module inifile to Litmus #344 (lionce)
- (FM-8154) Add Windows Server 2019 support #340 (eimlav)
- (FM-8041) Add RedHat 8 support #339 (eimlav)
v3.0.0 - 2019-05-09
Changed
- pdksync - (MODULES-8444) - Raise lower Puppet bound #335 (david22swan)
Fixed
2.5.0 - 2019-01-07
Added
- (MODULES-8142) - Addition of support for SLES 15 #315 (david22swan)
- (MODULES-7560) - removed spaces from the beginning or from the end of the value #311 (lionce)
- MODULES-1821 support empty sections #274 (cjepeway)
Fixed
- pdksync - (FM-7655) Fix rubygems-update for ruby < 2.3 #320 (tphoney)
- (MODULES-6714) - inifile: ensure absent not working with refreshonly = true #313 (Lavinia-Dan)
- (FM-7483) - update module to the latest version #310 (lionce)
- (FM-7331)-Fix japanese test #308 (lionce)
2.4.0 - 2018-09-28
Added
- pdksync - (FM-7392) - Puppet 6 Testing Changes #300 (pmcmaw)
- pdksync - (MODULES-7658) use beaker4 in puppet-module-gems #296 (tphoney)
- (MODULES-7552) - Addition of support for Ubuntu 18.04 to inifile #292 (david22swan)
Fixed
2.3.0 - 2018-07-05
Added
Fixed
2.2.2 - 2018-05-10
Fixed
2.2.1 - 2018-04-17
2.2.0 - 2018-01-29
Added
2.1.1 - 2017-12-07
Added
- Rubocop checks will now be run against any PRs made towards the module #251 (david22swan)
2.1.0 - 2017-12-01
Changed
Other
- MODULES-3624 Allow setting indent character #237 (jamesmcdonald)
2.0.0 - 2017-07-24
Changed
- MODULES-4830 Updating Puppet version requirement #236 (HelenCampbell)
Added
Fixed
- (MODULES-5172) Backwards compatible ini_file.set_value #240 (mwhahaha)
- (MODULES-4932) fix for mimicking commented settings #239 (eputnam)
- (MODULES-4170) Fix path validation on windows #224 (mullr)
1.6.0 - 2016-09-06
Added
- Add insert_type and subsetting_key_val_separator #208 (dmitryilyin)
- Added refreshonly Parameter #207 (jonnytdevops)
Fixed
- (MODULES-3472) Fix backwards compatability for create_ini_settings #211 (HelenCampbell)
- (MODULES-3145) Cast values to strings before passing to provider #204 (hunner)
1.5.0 - 2016-03-09
Added
- Remove empty sections after last setting is removed #199 (hunner)
- Update metadata to note Debian 8 support #198 (DavidS)
- Added keep_secret parameter feature #152 (stepanstipl)
Fixed
1.4.3 - 2015-12-07
1.4.2 - 2015-09-01
Added
- Adding path to create_ini_settings resources #185 (danzilio)
- [MODULES-2369] Support a space as a key_val_separator #184 (glarizza)
- MODULES-2212 - Add use_exact_match parameter for subsettings #182 (underscorgan)
Fixed
1.4.1 - 2015-07-29
1.4.0 - 2015-07-08
Added
- Add support for Solaris 12 #172 (drewfisher314)
Fixed
- MODULES-1599 Match only on space and tab whitespace after k/v separator #171 (misterdorm)
1.3.0 - 2015-06-09
Added
- Adding the ability to change regex match for $section in inifile #159 (WhatsARanjit)
- Flexible key val #139 (underscorgan)
- introduce create_ini_settings #129 (duritong)
Fixed
- Modules 1876 - Setting names containing spaces fail #158 (bmjen)
- Adds default values for section #157 (hunner)
- Less restrictive setting names #134 (johnsyweb)
1.2.0 - 2014-11-10
Fixed
1.1.4 - 2014-09-30
1.1.3 - 2014-07-15
1.1.2 - 2014-07-09
1.1.1 - 2014-07-07
Fixed
1.1.0 - 2014-06-05
1.0.4 - 2014-06-04
Added
- Add RHEL7 and Ubuntu 14.04 support. #97 (apenney)
- Add quote_char parameter to the ini_subsetting resource type #95 (mruzicka)
1.0.3 - 2014-03-03
1.0.1 - 2014-02-12
Added
Fixed
- Update settings regexes to support settings containing square brackets #65 (shrug)
- Support spaces in sections #58 (jnewland)
1.0.0 - 2013-07-16
Fixed
- Support for whitespaces in settings names #53 (apenney)
- Properly handle empty values #52 (otherwiseguy)
- Bug/inherited purging #50 (richardc)
- Bug/master/better handling of quotes for subsettings #47 (cprice404)
0.10.3 - 2013-05-28
Fixed
0.10.2 - 2013-05-22
0.10.1 - 2013-05-21
0.10.0 - 2013-04-02
Added
- Added 'ini_subsetting' custom resource type #29 (kbrezina)
- Add purging support to ini file #25 (bodepd)
Fixed
0.9.0 - 2012-11-02
Added
- Add detection for commented versions of settings #20 (cprice404)
- Feature/master/use existing indentation #19 (cprice404)
- Feature/master/tweaks to setting removal #18 (cprice404)
- add ensure=absent support #17 (bodepd)
Fixed
0.0.3 - 2012-09-24
Added
- Allow overriding separator string between key/val pairs #9 (cprice404)
- Added support for colons in section names #5 (jtopjian)
0.0.2 - 2012-08-20
0.0.1 - 2012-08-16
Dependencies
- puppetlabs/stdlib (>= 4.13.0 < 10.0.0)
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Quality checks
We run a couple of automated scans to help you assess a module’s quality. Each module is given a score based on how well the author has formatted their code and documentation and select modules are also checked for malware using VirusTotal.
Please note, the information below is for guidance only and neither of these methods should be considered an endorsement by Puppet.
Malware scan results
The malware detection service on Puppet Forge is an automated process that identifies known malware in module releases before they’re published. It is not intended to replace your own virus scanning solution.
Learn more about malware scans- Module name:
- puppetlabs-inifile
- Module version:
- 6.1.1
- Scan initiated:
- March 10th 2024, 20:41:53
- Detections:
- 0 / 61
- Scan stats:
- 61 undetected
- 0 harmless
- 0 failures
- 0 timeouts
- 0 malicious
- 0 suspicious
- 16 unsupported
- Scan report:
- View the detailed scan report