registry
Version information
This version is compatible with:
- Puppet Enterprise 3.x
- Puppet >= 3.3.0
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-registry', '1.1.0'
Learn more about managing modules with a PuppetfileDocumentation
####Table of Contents
- Overview - What is the registry module?
- Module Description - What registry does and why it is useful
- Setup - The basics of getting started with registry
- Usage - Configuration options and additional functionality
- Reference
- Limitations
- Development - Guide for contributing to registry
##Overview
This module supplies the types and providers you'll need to manage the Registry on your Windows nodes.
##Module Description
The Registry is a hierarchical database built into Microsoft Windows. It stores settings and other information for the operating system and a wide range of applications. This module lets Puppet manage individual Registry keys and values, and provides a simplified way to manage Windows services.
##Setup
This module must be installed on your Puppet master. We've tested it with Puppet agents running on Windows Server 2003, 2008 R2, 2012, and 2012 R2.
###Beginning with registry
Use the registry_key
type to manage a single registry key:
registry_key { 'HKLM\System\CurrentControlSet\Services\Puppet':
ensure => present,
}
##Usage
The registry module works mainly through two types: registry_key
and registry_value
. These types combine to let you specify a Registry container and its intended contents.
###Manage a single Registry value
registry_value { 'HKLM\System\CurrentControlSet\Services\Puppet\Description':
ensure => present,
type => string,
data => "The Puppet Agent service periodically manages your configuration",
}
###Manage a Registry value and its parent key in one declaration
class myapp {
registry::value { 'puppetmaster':
key => 'HKLM\Software\Vendor\PuppetLabs',
data => 'puppet.puppetlabs.com',
}
}
Puppet looks up the key 'HKLM\Software\Vendor\PuppetLabs' and makes sure it contains a value named 'puppetmaster' containing the string 'puppet.puppetlabs.com'.
Note: the registry::value
define only manages keys and values in the system-native architecture. In other words, 32-bit keys applied in a 64-bit OS aren't managed by this define; instead, you must use the types, registry_key
and registry_value
individually.
Within this define, you can specify multiple Registry values for one Registry key and manage them all at once.
###Set the default value for a key
registry::value { 'Setting0':
key => 'HKLM\System\CurrentControlSet\Services\Puppet',
value => '(default)',
data => "Hello World!",
}
You can still add values in a string (or array) beyond the default, but you can only set one default value per key.
###Purge existing values
By default, if a key includes additional values besides the ones you specify through this module, Puppet leaves those extra values in place. To change that, use the purge_values => true
parameter of the registry_key
resource. Enabling this feature deletes any values in the key that are not managed by Puppet.
The registry::purge_example
class provides a quick and easy way to see a demonstration of how this works. This example class has two modes of operation determined by the Facter fact PURGE_EXAMPLE_MODE
: 'setup' and 'purge'.
To run the demonstration, make sure the registry::purge_example
class is included in your node catalog, then set an environment variable in PowerShell. This sets up a Registry key that contains six values.
PS C:\> $env:FACTER_PURGE_EXAMPLE_MODE = 'setup'
PS C:\> puppet agent --test
notice: /Stage[main]/Registry::Purge_example/Registry_key[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value3]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value2]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_key[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\SubKey]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value5]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value6]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\SubKey\Value1]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value1]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\SubKey\Value2]/ensure: created
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value4]/ensure: created
notice: Finished catalog run in 0.14 seconds
Switching the mode to 'purge' causes the class to only manage three of the six registry_value
resources. The other three are purged because they are not specifically declared in the manifest.
Notice how Value4, Value5 and Value6 are being removed.
PS C:\> $env:FACTER_PURGE_EXAMPLE_MODE = 'purge'
PS C:\> puppet agent --test
notice: /Registry_value[hklm\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value4]/ensure: removed
notice: /Registry_value[hklm\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value6]/ensure: removed
notice: /Registry_value[hklm\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value5]/ensure: removed
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value3]/data: data changed 'key3' to 'should not be purged'
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value2]/data: data changed '2' to '0'
notice: /Stage[main]/Registry::Purge_example/Registry_value[HKLM\Software\Vendor\Puppet Labs\Examples\KeyPurge\Value1]/data: data changed '1' to '0'
notice: Finished catalog run in 0.16 seconds
###Manage Windows services
The registry::service
define manages entries in the Microsoft service control framework by automatically manipulating values in the key HKLM\System\CurrentControlSet\Services\$name.
This is an alternative approach to using INSTSRV.EXE 1.
registry::service { puppet:
ensure => present,
display_name => "Puppet Agent",
description => "Periodically fetches and applies configurations from a Puppet master server.",
command => 'C:\PuppetLabs\Puppet\service\daemon.bat',
}
##Reference
###Public Defines
registry::value
: Manages the parent key for a particular value. If the parent key doesn't exist, Puppet automatically creates it.registry::service
: Manages entries in the Microsoft service control framework by manipulating values in the key HKLM\System\CurrentControlSet\Services\$name.
###Public Types
registry_key
: Manages individual Registry keys.registry_value
: Manages individual Registry values.
###Parameters
####registry::value
:
#####key
Required. Specifies a Registry key for Puppet to manage. If any of the parent keys in the path don't exist, Puppet creates them automatically. Valid options: a string containing a Registry path.
#####data
Required. Provides the contents of the specified value. Valid options: a string by default; an array if specified through the type
parameter.
#####type
Optional. Sets the data type of the specified value. Valid options: 'string', 'array', 'dword', 'qword', 'binary', and 'expand'. Default value: 'string'.
#####value
Optional. Determines what Registry value(s) to manage within the specified key. To set a Registry value as the default value for its parent key, name the value '(default)'. Valid options: a string. Default value: the title of your declared resource.
####registry_key
#####ensure
Tells Puppet whether the key should or shouldn't exist. Valid options: 'present' and 'absent'. Default value: 'present'.
#####path
Required. Specifies a Registry key for Puppet to manage. If any of the parent keys in the path don't exist, Puppet creates them automatically. Valid options: a string containing a Registry path. For example: 'HKLM\Software' or 'HKEY_LOCAL_MACHINE\Software\Vendor'.
If Puppet is running on a 64-bit system, the 32-bit Registry key can be explicitly managed using a prefix. For example: '32:HKLM\Software'.
#####purge_values
Optional. Specifies whether to delete any values in the specified key that are not managed by Puppet. Valid options: 'true' and 'false'. Default value: 'false'.
For more on this parameter, see the Purge existing values section under Usage.
####registry_value
#####path
Optional. Specifies a Registry value for Puppet to manage. Valid options: a string containing a Registry path. If any of the parent keys in the path don't exist, Puppet creates them automatically. For example: 'HKLM\Software' or 'HKEY_LOCAL_MACHINE\Software\Vendor'. Default value: the title of your declared resource.
If Puppet is running on a 64-bit system, the 32-bit Registry key can be explicitly managed using a prefix. For example: '32:HKLM\Software\Value3'.
#####ensure
Tells Puppet whether the value should or shouldn't exist. Valid options: 'present' and 'absent'. Default value: 'present'.
#####type
Optional. Sets the data type of the specified value. Valid options: 'string', 'array', 'dword', 'qword', 'binary', and 'expand'. Default value: 'string'.
#####data
Required. Provides the contents of the specified value. Valid options: a string by default; an array if specified through the type
parameter.
####registry::service
#####ensure
Tells Puppet whether the service should or shouldn't exist. Valid options: 'present' and 'absent'. Default value: 'present'.
#####display_name
Optional. Provides a Display Name for the service. Valid options: a string. Default value: the title of your declared resource.
#####description
Optional. Provides a description of the service. Valid options: a string. Default value: blank.
#####command
Required. Specifies the command to execute when starting the service. Valid options: a string containing the absolute path to an executable file.
#####start
Required. Specifies the starting mode of the service. Valid options: 'automatic', 'manual', and 'disabled'.
Puppet's native service resource can also be used to manage this setting.
##Limitations
- Keys within HKEY_LOCAL_MACHINE (hklm) or HKEY_CLASSES_ROOT (hkcr) are supported. Other predefined root keys (e.g., HKEY_USERS) are not currently supported.
- Puppet doesn't recursively delete Registry keys.
Please report any issues through our Module Issue Tracker.
##Development
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.
Types in this module release
##2015-03-24 - Supported Release 1.1.0 ###Summary
This release adds support for Ruby 2.1.5 and issues with how Ruby reads back the registry in certain scenarios, see MODULES-1723 for more details.
####Bugfixes
- Additional tests for purge_values
- Use wide character registry APIs
- Test Ruby Registry methods uncalled
- Introduce Ruby 2.1.5 failing tests
##2014-08-25 - Supported Release 1.0.3 ###Summary
This release adds support for native x64 ruby and puppet 3.7, and bugfixes issues with non-leading-zero binary values in regestry keys.
##2014-07-15 - Supported Release 1.0.2 ###Summary
This release merely updates metadata.json so the module can be uninstalled and upgraded via the puppet module command.
##2014-05-20 - Supported Release 1.0.1 #####Bugfixes
- Add zero padding to binary single character inputs
##2014-03-04 - Supported Release 1.0.0 ###Summary This is a supported release.
####Bugfixes
- Documentation updates
- Add license file
####Known Bugs
- This module does not work if run as non-root. Please see PE-2772
##2013-08-01 - Release 0.1.2 ###Summary: This is a bugfix release that allows the module to work more reliably on x64 systems and on older systems such as 2003. Also fixes compilation errors due to windows library loading on *nix masters.
####Bugfixes:
- Refactored code into PuppetX namespace
- Fixed unhandled exception when loading windows code on *nix
- Updated README and manifest documentation
- Only manage redirected keys on 64 bit systems
- Only use /sysnative filesystem when available
- Use class accessor method instead of class instance variable
- Add geppetto project file
2012-05-21 - 0.1.1 - Jeff McCune jeff@puppetlabs.com
- (#14517) Improve error handling when writing values (27223db)
- (#14572) Fix management of the default value (f29bdc5)
2012-05-16 - 0.1.0 - Jeff McCune jeff@puppetlabs.com
- (#14529) Add registry::value defined type (bf44208)
2012-05-16 - Josh Cooper josh+github@puppetlabs.com
- Update README.markdown (2e9e45e)
2012-05-16 - Josh Cooper josh+github@puppetlabs.com
- Update README.markdown (3904838)
2012-05-15 - Josh Cooper josh@puppetlabs.com
- (Maint) Add type documentation (82205ad)
2012-05-15 - Josh Cooper josh+github@puppetlabs.com
- Remove note about case-sensitivity, as that is no longer an issue (5440a0e)
2012-05-15 - Jeff McCune jeff@puppetlabs.com
- (#14501) Fix autorequire case sensitivity (d5c12f0)
2012-05-15 - Jeff McCune jeff@puppetlabs.com
- (maint) Remove RegistryKeyPath#{valuename,default?} methods (29db478)
2012-05-14 - Jeff McCune jeff@puppetlabs.com
- Add acceptance tests for registry_value provider (6285f4a)
2012-05-14 - Jeff McCune jeff@puppetlabs.com
- Eliminate RegistryPathBas#(default?,valuename) from base class (2234f96)
2012-05-14 - Jeff McCune jeff@puppetlabs.com
- Memoize the filter_path method for performance (6139b7d)
2012-05-11 - Jeff McCune jeff@puppetlabs.com
- Add Registry_key ensure => absent and purge_values coverage (cfd3789)
2012-05-11 - Jeff McCune jeff@puppetlabs.com
- Fix cannot alias error when managing 32 and 64 bit versions of a key (3a2f260)
2012-05-11 - Jeff McCune jeff@puppetlabs.com
- Add registry_key creation acceptance test (0e68654)
2012-05-09 - Jeff McCune jeff@puppetlabs.com
- Add acceptance tests for the registry type (0a01b11)
2012-05-08 - Jeff McCune jeff@puppetlabs.com
- Update type description strings (c69bf2d)
2012-05-05 - Jeff McCune jeff@puppetlabs.com
- Separate the implementation of the type and provider (4e06ae5)
2012-05-04 - Jeff McCune jeff@puppetlabs.com
- Add watchr script to automatically run tests (d5bce2d)
2012-05-04 - Jeff McCune jeff@puppetlabs.com
- Add registry::compliance_example class to test compliance (0aa8a68)
2012-05-03 - Jeff McCune jeff@puppetlabs.com
- Allow values associated with a registry key to be purged (27eaee3)
2012-05-01 - Jeff McCune jeff@puppetlabs.com
- Update README with info about the types provided (b9b2d11)
2012-04-30 - Jeff McCune jeff@puppetlabs.com
- Add registry::service defined resource example (57c5b59)
2012-04-25 - Jeff McCune jeff@puppetlabs.com
- Add REG_MULTI_SZ (type => array) implementation (1b17c6f)
2012-04-26 - Jeff McCune jeff@puppetlabs.com
- Work around #3947, #4248, #14073; load our utility code (a8d9402)
2012-04-24 - Josh Cooper josh@puppetlabs.com
- Handle binary registry values (4353642)
2012-04-24 - Josh Cooper josh@puppetlabs.com
- Fix puppet resource registry_key (f736cff)
2012-04-23 - Josh Cooper josh@puppetlabs.com
- Registry keys and values were autorequiring all ancestors (0de7a0a)
2012-04-24 - Jeff McCune jeff@puppetlabs.com
- Add examples of current registry key and value types (bb7e4f4)
2012-04-23 - Josh Cooper josh@puppetlabs.com
- Add the ability to manage 32 and 64-bit keys/values (9a16a9b)
2012-04-23 - Josh Cooper josh@puppetlabs.com
- Remove rspec deprecation warning (94063d5)
2012-04-23 - Josh Cooper josh@puppetlabs.com
- Rename registry-specific util code (cd2aaa1)
2012-04-20 - Josh Cooper josh@puppetlabs.com
- Fix autorequiring when using different root key forms (b7a1c39)
2012-04-19 - Josh Cooper josh@puppetlabs.com
- Refactor key and value paths (74ebc80)
2012-04-19 - Josh Cooper josh@puppetlabs.com
- Encode default-ness in the registry path (64bba67)
2012-04-19 - Josh Cooper josh@puppetlabs.com
- Better validation and testing of key paths (d05d1e6)
2012-04-19 - Josh Cooper josh@puppetlabs.com
- Maint: Remove more crlf line endings (e9f00c1)
2012-04-19 - Josh Cooper josh@puppetlabs.com
- Maint: remove windows cr line endings (0138a1d)
2012-04-18 - Josh Cooper josh@puppetlabs.com
- Rename
default
parameter (f45af86)
2012-04-18 - Josh Cooper josh@puppetlabs.com
- Fix modifying existing registry values (d06be98)
2012-04-18 - Josh Cooper josh@puppetlabs.com
- Remove debugging (8601e92)
2012-04-18 - Josh Cooper josh@puppetlabs.com
- Always split the path (de66832)
2012-04-18 - Josh Cooper josh@puppetlabs.com
- Initial registry key and value types and providers (065d43d)
Dependencies
- puppetlabs/stdlib (>= 2.3.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 2013 Puppet Labs 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.