Dang Nguyen

File resource assertions for symlinks seem to contradict with file assertions

2

# Describe the problem Following the example described here: https://docs.chef.io/inspec/resources/file/#test-if-a-file-is-a-symbolic-link, I am seeing that the symlink and file assertions are contradicting. My resource: ``` describe file('/usr/bin/pip') do its('type') { should...

yum resource should support all configurable yum repo settings

2

## Detailed Description Currently, the `yum.repo` resource supports only a handful of possible yum configuration properties. This is a very limited short list of properties to check. Can we support...

Add a graceful-restart option in service restart script

1

### Cookbook version 8.1.7 ### Chef-client version 12.14.89 ### Platform Details Redhat and CentOS 6 & 7 ### Scenario: After log rotation with logrotated, the postrotate option in this cookbook...

We've had chef run failures during a large scale-up event in our autoscaling group. Each instance of the autoscaling group that comes online adds itself to the same DNS CNAME...

Fix interpolation issue in the splunk_login_successful method

22

# Description - Fixes Issue [#204](https://github.com/sous-chefs/chef-splunk/issues/204) - Fixes an issue with the `user-seed.conf` file - Ensures that splunk is installed prior to anything in the `chef-splunk::service` recipe executes ## Issues...

## :ghost: Brief Description `#splunk_login_successful?` helper method contains an interpolation error resulting in the static string `node.run_state['splunk_auth_info']` being passed to `#splunk_cmd` instead of the actual value of the run_state attribute....

Extend #395 to accommodate extra_endpoints

4

Datadog auth secrets are also stored in extra_endpoints, `node['datadog']['extra_endpoints']`, but #395 fell short in that it didn't cover these attributes. These should also be retrieved from node run state whenever...

We are wrapping this cookbook and in one of our recipes, we're issuing `include_recipe 'datadog::dd-handler'. The chef run fails with only the values set by the datadog cookbook's default attribute...

https://github.com/DataDog/chef-datadog/blob/master/attributes/default.rb#L34-L37 should be commented out

2

https://github.com/DataDog/chef-datadog/blob/master/attributes/default.rb#L34-L37 show an example of configuring extra endpoints for an agent, like so: ``` default['datadog']['extra_endpoints']['prod'] ``` However, we've never had the need for this actually being in our extra endpoints....

repository should not enforce gpgcheck when gpgkey is nil or empty String

3

`node['datadog']['gpgkey']` can now be set to nil or empty String. This should automatically set the yum_repository resource to false. ``` yum_repository 'datadog' do name 'datadog' description 'datadog' url node['datadog']['yumrepo'] proxy...