summaryrefslogtreecommitdiff
path: root/lib/chef/resource/apt_preference.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove the canonical DSLLamont Granquist2020-03-031-2/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* WIP: Chef-16 resource cleanup + unified_mode (#9174)Lamont Granquist2020-01-211-1/+69
| | | | | | * Chef-16 resource cleanup + unified_mode Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix Layout/AlignArgumentslcg/new-chefstyleLamont Granquist2019-07-021-9/+9
| | | | | | | | | | | | | | this is using: Layout/AlignArguments: Enabled: true EnforcedStyle: with_fixed_indentation the default style can use really excessive whitespace. on starting lines which are already long, it fully indents across to where the arguments start and then begins the line there. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix a bunch of weirdly mangled require linesLamont Granquist2019-05-081-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Convert require to require_relativeLamont Granquist2019-05-081-1/+1
| | | | | | | This gives a speed boost since rubygems does not have to scan through every gem in the gemset in order to find the file. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Improve resource descriptions for documentationTim Smith2018-11-141-1/+1
| | | | | | Mostly cleaning up how we describe name properties, but also copying over some edits that happened on the docs site. Signed-off-by: Tim Smith <tsmith@chef.io>
* Add more validation_messages to propertiesvalidationsTim Smith2018-11-031-1/+2
| | | | | | Provide users with more helpful messages Signed-off-by: Tim Smith <tsmith@chef.io>
* Add missing periods and rely on word wrapcleanupTim Smith2018-04-271-3/+1
| | | | | | Just stick the descriptions on a single line so that we utilize large monitors. Signed-off-by: Tim Smith <tsmith@chef.io>
* Modify the provides for all resources from cookbooks so chef winsprovidesTim Smith2018-04-061-1/+1
| | | | | | Due to changes in chef-client 14 old cookbooks started winning and this causes lots of problems, especially for old incompatible resources. Chef client should always win here. Signed-off-by: Tim Smith <tsmith@chef.io>
* More documentation updates for resourcesTim Smith2018-03-161-4/+15
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Add new introduced and description resource properties to many resourceTim Smith2018-02-141-3/+5
| | | | | | Not all of them, but a good chunk. Signed-off-by: Tim Smith <tsmith@chef.io>
* Add descriptions and @since comments to all resourcesTim Smith2017-12-191-0/+4
| | | | | | From the docs site Signed-off-by: Tim Smith <tsmith@chef.io>
* Open apt resources up to prevent breaking changeapt_openTim Smith2017-09-171-1/+1
| | | | | | | | | If we want these to throw a no ops vs. a hard failure we need them to be wide open. Since a lot of people (including all of chef-cookbooks) have coded as if these will gracefully skip this would have been a breaking change. Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the usage of an array for the platform_familyapt_resourcesTim Smith2017-09-141-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Replace which apt-get check with simple debian check in apt resourcesTim Smith2017-09-141-1/+1
| | | | | | apt-get is a link to yast2 in suse so these resources fire there when someone wouldn't expect them to. Looking back we probably should have skipped the whole platform based no-op thing, but that ship sailed. This makes it behave the way a user would expect it to. What happens if you have apt compiled on your gentoo box? Well it's going to break. We'll just have to live with fixing it for 99.99% of users instead of the current 95%. Also: This is faster. Signed-off-by: Tim Smith <tsmith@chef.io>
* Testing updatesTim Smith2017-05-121-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Chefstyle fixesTim Smith2017-05-121-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Wire up provider/resource and use constants so we can testTim Smith2017-05-121-1/+1
| | | | | | Also allow the pin priority to be an integer since there's no reason that needs to be a string Signed-off-by: Tim Smith <tsmith@chef.io>
* Require pin/pin_priority and update copyrightsTim Smith2017-05-121-3/+3
| | | | | | The resource fails without these values. Let's require them to give the user a proper error message Signed-off-by: Tim Smith <tsmith@chef.io>
* Initial apt_preference commitTim Smith2017-05-121-0/+36
Specs are a placeholder on the provider side Signed-off-by: Tim Smith <tsmith@chef.io>