Add Logs Restrictions Query support

[ohookins]

Note:
If you have a feature request, you should contact support so the request can be properly tracked.

Is your feature request related to a problem? Please describe.
We'd like to use the Log Restrictions Queries feature via Terraform which would necessitate it being added to the Go client. It's not currently implemented here.

Describe the solution you'd like
Support for that API implemented in the client.

Describe alternatives you've considered
N/A

Additional context
N/A

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[mmpashby]

I'd love to see this due to some tooling or IaC requirements we have.

[jirikuncar]

We are planning to release this feature in API clients in next few weeks.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[thangnc]

@jirikuncar do you have plan to release this feature in this Jun? Since we want to use Terraform to restrict log queries but it depends on Datadog API client 😢

[jtrochim2]

I would love to use that feature too!

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

What is the latest status on this issue ?

[thangnc]

@Kerwood it does not seem to have PR for this issue. That's why im working on the branch to support it.

[Kerwood]

@thangnc That is great news :)
Where do I keep my self updated? On this specific issue ?

[thangnc]

@Kerwood i open the tmp PR to my Git repo here thangnc#1. Will switch to main repo https://github.com/DataDog/datadog-api-client-go when i finish the feature :)

[thangnc]

Sorry @Kerwood, i've just checked carefully again. The Go code in this repo was generated automatically via https://github.com/DataDog/datadog-api-spec repo. But this repo is private repo, then we need to wait Datadog to supports this feature. I close my PR since its never to be merged

[Kerwood]

Ok.. Let's hope they prioritize it :)

[thangnc]

@skarimo @therve can you help to support this feature? Since Terraform provider is depending on this lib?

[therve]

We talked to the logs backend team and they plan to do some changes to that API, so they'd like to not support the current version in SDK for now. Hopefully we'll hear more soon, thanks for your patience.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

This issue is still relevant.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

Still needed...

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

Still relevant....

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

Still needed

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

Still relevant

[SharpEdgeMarshall]

@therve would you mind providing an update to us, considering we are paying enterprise customers?

[mikebou]

@jirikuncar I am also interested an update. I appreciate the desire to do this work once but either the api update is not a priority as that statement was a year, could we get an update to the module to leverage the existing functionality please!

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[Kerwood]

Still relevant

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.

[K4pper]

Still relevant

[hobbyhorse]

@Kerwood you are a hero for how long you have been following up on this.

Come on Datadog. You are using a code generator for this repo, so while it is open source, it really isn't.

It has been YEARS since you released the feature and we still only have console support. Yeah, we can roll our own, and I have in python, but I want to maintain state in TF along with the rest of my stuff.

Please, please.

[thangnc]

@hobbyhorse this is open source repo but we can not contribute for this. I dont really understand why Datadog opened source this repo :)

[albertocavalcante]

How can we seriously get some progress here? Thanks