summaryrefslogtreecommitdiff
path: root/lib/chef/resource
Commit message (Collapse)AuthorAgeFilesLines
* windows_package installer_type should be a symbolBryan McLellan2014-10-301-1/+1
| | | | | | | Fixes #1997 Conflicts: spec/unit/resource/windows_package_spec.rb
* Merge pull request #2313 from opscode/sersut/win-res-lookup-fixSerdar Sutay2014-10-302-2/+4
| | | | | | Make sure windows_service and windows_package resources are found with the new dynamic provider resolver. Conflicts: spec/unit/resource/windows_package_spec.rb
* Merge pull request #1596 from opscode/lcg/provider-resovlerLamont Granquist2014-10-2445-54/+75
|\ | | | | CHEF-3404: Provider Resolver
| * Chef-12 RC Provider ResolverLamont Granquist2014-10-2445-54/+75
| | | | | | | | | | makes resource and provider class resolution more dynamic. begins deprecation of Chef::Platform static mapping.
* | Set guard_interpreter using default_guard_interpreterAdam Edwards2014-10-231-1/+1
| |
* | powershell_script and batch resource guard_interpeter default to parent resourceAdam Edwards2014-10-232-2/+3
|/
* Set the :default_guard_interpreter to :default so that the script resource ↵Serdar Sutay2014-10-201-0/+1
| | | | guards are executed correctly.
* Merge pull request #2216 from opscode/tball/bsd_package_nameTyler Ball2014-10-171-12/+0
|\ | | | | Notify a resource by the `resource[name]` key it was written as
| * Removing all traces of 'created_as_type' since that fix is no longer necessarytyler-ball2014-10-161-12/+0
| |
* | Differentiate between the default and the user set guard_attributes in order ↵Serdar Sutay2014-10-162-21/+17
| | | | | | | | to be able to warn users correctly when they configure a guard_attribute but use a ruby block in the guard.
* | Enable guard_interpreters for the execute resource and set the default ↵Serdar Sutay2014-10-163-39/+45
| | | | | | | | | | | | interpreter for the execute resource to be :execute. This ensures that attributes of the resource like :environment & :cwd can be inherited by the guard when guard is specified as a string.
* | Remove the "path" attribute from "execute" resource which has never been ↵Serdar Sutay2014-10-161-9/+0
|/ | | | backed by any providers.
* Merge pull request #2165 from coderanger/rfc017Serdar Sutay2014-10-102-2/+2
|\ | | | | RFC 17 implementation
| * Rework template/file loading to not require the default/ and to accept an ↵Noah Kantrowitz2014-10-042-2/+2
| | | | | | | | | | | | | | array for explicit search path manipulation. This is the backwards compatible solution to migrate away from the implicit search path in favor of making it explicit when needed (which is rarely). Conflicts: lib/chef/cookbook_version.rb
* | Merge pull request #1907 from Aevin1387/freebsd-port-pkgngSerdar Sutay2014-10-101-12/+11
|\ \ | | | | | | Have freebsd port use pkg info if the freebsd version is >= 10000017
| * | Move supports_with_pkgng? check to the freebsd_package package.Cory Stephenson2014-08-281-11/+10
| | |
| * | Have freebsd port use pkg info if the freebsd version is >= 10000017Cory Stephenson2014-08-241-2/+2
| | |
* | | Merge pull request #2197 from opscode/sersut/fixup-chef-1662Serdar Sutay2014-10-091-1/+12
|\ \ \ | | | | | | | | Keep deprecation of valid_actions until Chef 13.
| * | | Revert "Remove appending :actions and :valid_actions"Serdar Sutay2014-10-091-1/+12
| | | | | | | | | | | | | | | | This reverts commit 4aec038d42eae5c3c3bac50aa211d2b69cf54019.
* | | | Updates based on PR comments.sersut/no-lwrp-class-reloadSerdar Sutay2014-10-091-1/+0
| | | |
* | | | Don't override LWRP resources or providers anymore in Chef 12.Serdar Sutay2014-10-081-13/+12
|/ / /
* | | Merge pull request #2103 from opscode/jdmundrawala/issue-2027-masterJay Mundrawala2014-10-081-16/+2
|\ \ \ | | | | | | | | We now check for powershell/dsc compat in provider.
| * | | We now check for powershell/dsc compat in provider.jdmundrawala/issue-2027-masterJay Mundrawala2014-09-221-16/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The problem with raising an exception when the resource is created was that it was not possible to have a chef recipe that installs the correct version of powershell and then runs the dsc_script resource. See https://github.com/opscode/chef/issues/2027
* | | | homebrew_owner now tries to run homebrew as the user who owns the `brew` ↵tyler-ball2014-10-071-0/+11
| |_|/ |/| | | | | | | | executable, or an optional homebrew_package resource attribute
* | | Remove duplicate exceptionBryan McLellan2014-09-301-1/+3
| | | | | | | | | | | | | | | We already check for command || block_given? in initialize, so command cannot be nil && not have a block when we get here.
* | | unit test for guard_interpreter creation during compilationBryan McLellan2014-09-301-0/+1
| | | | | | | | | | | | | | | | | | make sure we don't evaluate the guard_interpreter immediately, i.e. during compilation of the resource, as the conditional may be seen before the guard_interpreter attribute.
* | | refactor conditional to evaluate for guards laterBryan McLellan2014-09-301-7/+17
| | | | | | | | | | | | | | | | | | | | | | | | If we don't create the guard_interpreter until we're ready to test it, we're sure to already have all the resource attributes evaluated. Previously we set up the guard_interpreter upon initialization, that is when it was first set on the resource.
* | | update functional tests for guard_interpreterBryan McLellan2014-09-301-1/+1
| | | | | | | | | | | | | | | | | | | | | we now raise an error when passed a block and a guard_interpreter is specified other than :default. When other interpreters become the "default" (which actually means use the default shell for that platform) we will need to consider those as well, i.e. #1495.
* | | guard_interpreter requires a commandBryan McLellan2014-09-301-0/+5
|/ / | | | | | | | | | | | | | | Raises an exception if guard_interpreter is set (not :default) and we are not given a command (i.e. we are given a block). This is not supported, as we pass a command to an external interpreter. Related to #1943
* | Restoring https://github.com/opscode/chef/pull/1921 to master - somehow it ↵tyler-ball2014-09-191-0/+34
| | | | | | | | got deleted from the git log
* | DscScript resource will raise an error if dsc is not availableJay Mundrawala2014-09-191-1/+18
| |
* | Add configurationdata attribute supportAdam Edwards2014-09-191-4/+26
| |
* | Initial dsc_configuration resource implementationAdam Edwards2014-09-191-0/+101
| |
* | Improve the action and throw-label names.Chris Doherty2014-09-121-2/+5
| |
* | Rename actions to :request_reboot_on_successful_run and :reboot_interrupt_run.Chris Doherty2014-09-101-1/+1
| |
* | Remove the timestamp attribute, which isn't actually settable by the user.Chris Doherty2014-09-101-4/+0
| |
* | 'timeout' -> 'delay_mins'; add a run_context() shim for RebootPending.Chris Doherty2014-09-101-3/+3
| |
* | First-pass changes for a core reboot resource. Still uses run_state instead ↵Chris Doherty2014-09-101-0/+49
|/ | | | of run_context.
* CHEF-1737: Fix noauto support.markgibbons2014-08-211-0/+9
| | | | | Add fsck device support. Allow vxfs device types.
* set nil by default, add two specssawanoboly2014-08-211-1/+1
|
* add_env_to_scm_resourcesawanoboly2014-08-211-0/+10
|
* Make sure freebsd_package is captured with the resource name it's declared ↵Serdar Sutay2014-08-131-2/+10
| | | | with in resource collection.
* * Dscl user provider changes to support Mac 10.7, 10.8 & 10.9.Serdar Sutay2014-08-121-0/+18
| | | | | | * Make the dscl user provider password handling idempotent. * Refactor / modernize dscl user provider unit tests. * Functional tests for dscl user provider.
* CHEF-5022: Add tests for #set_start_type and cleanupBryan McLellan2014-08-121-2/+1
|
* CHEF-5022: Don't use provides in the resourceBryan McLellan2014-08-121-1/+4
| | | | | | | Wait until #1773 is fixed to use provides in the resource. This means you need to specify windows_service in your recipes if you want to use the :configure_startup action and the startup_type attribute.
* CHEF-5022: Add configure_startup actionBryan McLellan2014-08-121-1/+2
| | | | | | enable and disable actions will continue to set the startup type to automatic/disabled If you want the startup type to be manual, you can set the startup_type attribute and use action configure_startup. It also supports automatic and disabled.
* CHEF-5022: Differentiate between Windows service startup_typesBryan McLellan2014-08-121-0/+50
| | | | | | | | | A Windows service startup_type can be automatic, manual, or disabled. This adds a startup_type attribute to specify automatic or manual, and defaults to automatic because we currently have no functionality to set a service to manual. This is important because if you stop a service that is automatic, Windows will change the startup_type to manual.
* Merge pull request #1680 from BundesIT/masterClaire McQuin2014-08-071-0/+1
|\ | | | | Some minor fixes for the Paludis package provider
| * whitespace fix in paludis_package.rbtbe2014-07-281-1/+1
| |
| * moved init of timeout for paludis packages to the right placeThomas Berger2014-07-261-0/+1
| |