| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Without this anything that's gpg signed will fail waiting for the user to accept or deny the key. If users don't want this I've provided a new property to disable it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@clogeny.com>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@clogeny.com>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Apt: Add apt_preference resource from apt cookbooks
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| | |
Specs are a placeholder on the provider side
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
* Added username/password validation for elevated option with specs
Signed-off-by: nimisha <nimisha.sharad@clogeny.com>
|
|\ \
| | |
| | | |
Add support for HTTP PATCH requests
|
| | |
| | |
| | |
| | | |
Signed-off-by: James Broadhead <james.broadhead@mongodb.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: NimishaS <nimisha.sharad@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
copypasta mistake from the old provider
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |/
|/|
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| |/
|/| |
Updated to fix day validation with monthly frequency
|
| |
| |
| |
| | |
This should fix issue #6104
Signed-off-by: Corey Hemminger <corey.hemminger@nativex.com>
|
|/
|
|
|
|
| |
* Added functional specs for windows_task resource
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
|
|
|
|
|
|
|
| |
where the tests assumed nillable properties.
This will get cleaned up when they are converted to real properties.
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
|
|
|
| |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
|\
| |
| | |
Adding windows_task resource
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I think this is better
- Chef::Config[:rubygems_uri] is nearly always applied (but
could be set to nil if someone really wanted to opt-out)
- the per-resources sources are additive on top of the
global config (lets cookbooks be additive to global config
rather than override it by default).
- there's a new flag for if you want to opt-out of the global
config completely on a per-resource basis.
So I think this gets the most commmon and the next most common
use cases correct, while still allow people with arbitrarily
crazy needs to write resources that do it.
The RELEASE_NOTES also have somewhat better user stories in them,
which I think suggests that I'm on the right track here.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| |
| |
| |
| |
| |
| | |
https://github.com/chef/chef/commit/81db0e0cfc218169a70a8178f83c567b467d2e6c
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By default now we don't pass any --source option or set the
`Chef::Config[:rubygems_url]` to anything. This is so that
if there is external config for rubygems sources we will simply
have rubygems pick it up and use it (the resource acts like
the command line).
There is also no more magic around `--clear-sources` and if you
set the property it sets the flag.
If the `Chef::Config[:rubygems_url]` setting is set then that
becomes the default `--source` flag sent to the command. This
also supports Arrays now.
If the `source` option is set to a URI (it can also be set to a
filesystem path for poorly-designed-API reasons) then we do not
use the default values at all. This may be an API break but this
much more clearly allows users to override individual resources
and is more declarative. You get what you type.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | |
| | | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| |\ \
| | | |
| | | | |
Launchd limit_load_to_session_type accepts Array or String
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Gregory Batye <gbatye@fb.com>
|
| |\ \ \
| | | | |
| | | | | |
Chef-13: Remove the consts for DSL-based resources/providers
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Adding restart action to launchd resource
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Mike Dodge <mikedodge04@gmail.com>
|
| | | |_|_|/ /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
At first we wanted only support native actions with the launchd
resource and launchd does not have the concept of restart. You would
unload and load. But not having a restart was causing more confusion to
people.
|
| |\ \ \ \ \ \
| | |_|_|_|/ /
| |/| | | | | |
systemd_unit verifier escape hatch
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Nathan Williams <nath.e.will@gmail.com>
|