summaryrefslogtreecommitdiff
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Update rubygems provider to support local install of gems if so specifiedksubrama+praj/FLOW-298/local_gemPrajakta Purohit2016-04-211-4/+8
|
* Extract common ChefFS file codeThom May2016-04-211-0/+128
|
* update to latest chefstyle - fix casecmptm/fix_casecmpThom May2016-04-202-2/+2
|
* ignore deprecation warning in testLamont Granquist2016-04-151-0/+1
|
* add better resource manipulation APILamont Granquist2016-04-152-0/+365
| | | | | deprecates chef_rewind functionality completely and adds a few more features
* add nillable apt_repository and nillable propertiesLamont Granquist2016-04-143-7/+32
| | | | | | in Chef-13 nillable will become 'true' by default and we'll have to deprecate and remove all nillable properties, but for now this lets us opt-in, which was can't currently do in Chef-12.
* ensure directory and file_system_entry are compatibleThom May2016-04-131-2/+2
|
* test ChefFS repo directory base classThom May2016-04-131-4/+8
|
* Add tests for ChefFS repo directory classThom May2016-04-131-0/+170
|
* add notifying_block and subcontext_block to chefLamont Granquist2016-04-111-0/+111
|
* Merge pull request #4812 from chef/salam/group-fixSalim Alam2016-04-112-5/+13
|\ | | | | Removing non-existent members from group should not fail
| * Update specssalam/group-fixSalim Alam2016-04-072-4/+11
| |
| * Don't fail when removing non-existing group memberSalim Alam2016-04-071-1/+2
| |
* | Merge pull request #4782 from chef/tm/apt_repositoryThom May2016-04-082-0/+212
|\ \ | |/ |/| Add apt_repository resource
| * Add an apt_repository resourcetm/apt_repositoryThom May2016-04-082-0/+212
| | | | | | | | | | More or less stolen from the apt cookbook, but tweaked and fixes a heap of bugs.
* | Merge pull request #4804 from chef/salam/knife-tweakSalim Alam2016-04-071-5/+6
|\ \ | | | | | | Add default timeout
| * | Fix specsalam/knife-tweakSalim Alam2016-04-061-5/+6
| | |
* | | Merge pull request #4750 from jkerry/SFTP_Remote_File_SupportLamont Granquist2016-04-061-0/+150
|\ \ \ | |/ / |/| | Sftp remote file support
| * | fixing rubocop violations, mostly string format, in the sftp provider and ↵John Kerry2016-03-251-3/+0
| | | | | | | | | | | | spec files
| * | Finishing off the sftp unit tests. Added some checks to the sftp provider to ↵John Kerry2016-03-241-4/+107
| | | | | | | | | | | | maintain the precedent set by the ftp provider
| * | Adding base implementation and the start of unit test coverageJohn Kerry2016-03-231-1/+18
| | |
| * | Adding the provider and spec files for sftpJohn Kerry2016-03-231-0/+33
| | |
* | | Merge pull request #4709 from coderanger/init_commandNoah Kantrowitz2016-04-051-0/+14
|\ \ \ | |_|/ |/| | Setting init_command should be accepted instead of specific command overrides
| * | Improved test coverage for behavior with *_command.Noah Kantrowitz2016-03-151-0/+14
| | |
* | | Add a NoOp providertm/provider_no_opThom May2016-04-041-0/+24
| | | | | | | | | | | | | | | | | | This allows one to have a resource which is really only appropriate for one platform, but available everywhere. Then you simply allow noop to provide the resource everywhere besides where it's supposed to be.
* | | Make notifications recursive.lcg/notify-scopesLamont Granquist2016-04-042-0/+404
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is similar to poise's approach but has a few differences. Similarly to poise, the base behavior of notifications and find() and lookup() on the resource collection is changed to be 'recursive' and to search in outer contexts for resources and will return them by default. There are find_local() and lookup_local() methods added to allow for bypassing the recursion and making sure to throw exceptions if the current run_context does not have any matching resources. The CHEF-3694 resource cloning code has been modified to call the lookup_local() API and not to be recursive because we believe that nobody in their right mind would want that behavior (and resource cloning should eventually be removed). So the behavior of resource cloning should remain unchanged. The behavior of delayed notifications to resources outside of the current run_context is slightly different than what Poise has been implementing. The delayed notification will run in the run_context of the resource that is being notified. I think Poise tends to bubble up to the nextmost wrapping resource context (as opposed to Poise's subcontext_block or notifying_block contexts). This code I think is conceptually simpler to reason about, and I think it gets the use case right where if you're notifying a service resource in the outermost run_context from within multiple wrapping resources that it correctly bubbles out to the outermost run context and will notify with all the other delayed notifications at the end of the chef client run. Another useful feature of the delayed notification behavior is that if we do implement notifying_block or subcontext_block that each block can get its own delayed notification run and any resources that are inside of that block can run in the delayed notification phase of that block (while still being able to notify resources outside of the block and having those delayed notifications run in the receiving resources run_context). This will let us implement an often-requested feature for having "notifications delayed to the end of a block/recipe" instead of having to do all notifications absolutely immediately or delayed to the end of the chef run. This code also cleans up the object model a little bit. All of the state about notification collection is now hanging off of the run_context -- the delayed_actions have been moved from the Chef::Runner to the Chef::RunContext. Hanging it off of the Chef::Runner would have been very difficult to 'target' from other run_context's without adding a pointer back from the RunContext to the Runner and that feels like the wrong object model. The RunContext is now responsible for all of its notification state, while the Runner is responsible for wiring up the notifications across different run_contexts. Note that it will not be possible to send a notification to a run_context which has already been converged. That seems to make sense to me and the search API on the resource collection does not support returning resources from run_contexts that are children, only parents (and we don't actually hold onto pointers to child run_contexts and they may be garbage collected).
* | | Revert "Spec break on Windows due to temp dir and short path names"Salim Alam2016-03-313-24/+2
| | | | | | | | | | | | This reverts commit e25b75e9fcd26ccc9c9094a43b614306de1047db.
* | | Merge pull request #4775 from chef/cd/mount-remount-optionsBryan McLellan2016-03-314-41/+1
|\ \ \ | | | | | | | | Revert PR #1796: make mount resource options-ignorant again.
| * | | Revert PR #1796.cd/mount-remount-optionsChris Doherty2016-03-314-41/+1
| | | | | | | | | | | | | | | | | | | | Closes issue #4056, although as discussed in that issue, we still need followup design and implementation work to make the mount resource behave in a safe and unsurprising way.
* | | | Spec break on Windows due to temp dir and short path namesadamedx/windows-ruby22-unit-tmpdirAdam Edwards2016-03-313-2/+24
|/ / /
* | | Merge pull request #4757 from tas50/better_mdLamont Granquist2016-03-311-48/+48
|\ \ \ | | | | | | | | Improve the docs generated by knife cookbook create
| * | | Chef the specsTim Smith2016-03-261-48/+48
| | | |
* | | | Merge pull request #4767 from chef/salam/timeoutSalim Alam2016-03-301-0/+17
|\ \ \ \ | | | | | | | | | | Add option to set knife ssh timeout
| * | | | Add option to set ssh timeoutsalam/timeoutSalim Alam2016-03-291-0/+17
| | |_|/ | |/| |
* | | | Add optional integer argument for --daemonize optionJordan Running2016-03-291-64/+124
| | | |
* | | | Add shorthand :syslog and :win_evt for log_location configjr/logger-configJordan Running2016-03-291-0/+27
| |/ / |/| |
* | | supresses parser gem errorsLamont Granquist2016-03-253-6/+6
|/ / | | | | | | | | | | see https://github.com/whitequark/parser/issues/283 if rubocop works around this bug then we can revert this patch.
* | Merge pull request #4744 from chef/salam/subversion-fixSalim Alam2016-03-231-14/+68
|\ \ | | | | | | Subversion provider should respect proxies
| * | Subversion provider should respect proxiesSalim Alam2016-03-221-14/+68
| | |
* | | Merge pull request #4670 from tas50/knife_wording-3Tim Smith2016-03-235-13/+13
|\ \ \ | |/ / |/| | Improve wording in Knife
| * | Fix failing specsTim Smith2016-03-065-13/+13
| | |
* | | Merge pull request #4732 from chef/lcg/use-inline-resources-coreLamont Granquist2016-03-222-11/+11
|\ \ \ | | | | | | | | allow use_inline_resources for core chef providers
| * | | allow use_inline_resources for core chef providersLamont Granquist2016-03-212-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * removes the DSL from InlineResources class * ActionClass is now responsible for mixing the DSL into action classes * apt_update provider converted over to use new syntax - does not need to mixin DeclareResource DSL - declares use_inline_resources - uses declare_resource instead of build_resource - converts def action_stuff to action :stuff - uses an execute resource instead of shell_out! - does not need the converge_by to update the action
* | | | Fix proxified socketSalim Alam2016-03-211-3/+6
| | | |
* | | | Update config specSalim Alam2016-03-211-1/+1
|/ / /
* | | Update launchd spec for doctype changedanielsdeleo2016-03-211-1/+1
| | |
* | | Make example classes #to_s method return a stringdebug-travis-provider-resolver-faildanielsdeleo2016-03-212-2/+2
| | |
* | | Merge pull request #4348 from chef/nls/proxy-cleanupChris Doherty2016-03-183-152/+69
|\ \ \ | | | | | | | | Make handling of proxies more consistent
| * | | Rubocop.Chris Doherty2016-03-171-4/+4
| | | |
| * | | Make handling of proxies more consistentNathan L Smith2016-03-173-154/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Always use `*_proxy` environment variables. * Make a `ChefConfig::Config.proxy_uri` method that gets used by `Chef::Provider::RemoteFile::FTP` and `Chef::HTTP::BasicClient`. * Remove `env` method from `Chef::HTTP::BasicClient` (using `stub_const("ENV", ...)` in specs instead.) * Remove `http_proxy_user` and `http_proxy_pass` methods from `Chef::HTTP::BasicClient` (replaced by functionality in `ChefConfig`.)
View Lorry Controller Status