Olivier Vielpeau

Thanks @iancward, makes sense, adding this to the `2.17.0` milestone

Thanks @gabinante for reporting this (and sorry I missed the issue), have you tried what I wrote here https://github.com/DataDog/chef-datadog/issues/488#issuecomment-348498502? As you noticed the current logic is pretty convoluted and needs...

Hi @chicks-net! By default, the 3 configuration options you've mentioned are set by this cookbook to the same values as those the agent uses by default, so even though the...

This could have been caused by a network failure during the `apt-get update` that's triggered when the repository is installed on the first run. Such a failure would cause the...

Ok, thanks for your feedback! IMO this issue can't be fixed cleanly until the following open issue on the `apt` cookbook has been resolved: https://github.com/chef-cookbooks/apt/issues/164

Going to move this back to a later release, the PR is not ready enough to be shipped with `2.8.0`. We should also discuss if it would be better to...

Hi @mlcooper! This statement is still valid unfortunately. On Windows, if you're using `Chef >= 12.6` and need to use `windows >= 1.39`, `3.0` included, you'll have to use the...

Thanks for your feedback @pmahoney! The `key_proxy` attribute has been added in version `2.8.0` of the `apt` cookbook (see https://github.com/chef-cookbooks/apt/pull/135). It's possible to set a proxy in earlier (and later)...

Hi @benorgil and sorry for the very late reply. To pin the version of the Agent that's installed by the cookbook, you should make sure `agent_package_action ` is left to...

This would be a welcome feature indeed. Are you still using the `extra_endpoints` on the Agent side? This was originally implemented mostly for our internal usage, but I'd be interested...