Slavek Kabrda

Hi 👋, thanks for opening this issue. My understanding of what happened is following: * You've been using ansible-datadog 4.2.1. This version didn't yet know about the new public APT...

So I tried temporarily disabling the datadog sources while installing the other packages and re-enabling them afterwards. There is a problem with this approach: APT doesn't know the concept of...

Hi 👋 thanks for opening this issue. Since `compliance_config` is a key expected to be present in `/etc/datadog-agent/datadog.yaml`, have you tried setting it through `datadog_config`, such as this: ``` vars:...

Hi folks, version 2.5.0 of the provider has been released and contains support for logs indexes and logs pipelines [1]. While I understand that the current feature set does not...

Hey @unthought, I think this issue was now fixed in the backend code - I'm no longer able to reproduce it. Could you please give it another try and let...

So I've been looking into this and it's almost impossible achieve with current TF internal functionality. Let me explain: * We basically need a dynamic default for `no_data_timeframe`, based on...

@phillip-dd the problem here is that if we do that, the user will always have a non-empty plan on running `terraform apply`, because the TF config will contain no value...

Thanks for the response. I actually never realized that there is such ambiguity in HCL itself. I think I'd rather wait for #1 get sorted out before implementing this. I'll...

I've also just run into this issue. Is there a way to make this work with "Rolling" strategy to have zero downtime upgrades?

Ok, that makes sense, thanks. If I wanted to solve this on higher logical layer, how would I go about this? Do you have any good pointers?