Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing to update with MonitorUpdateRequest #2043

Open
Doetheman opened this issue Jul 12, 2024 · 2 comments
Open

Failing to update with MonitorUpdateRequest #2043

Doetheman opened this issue Jul 12, 2024 · 2 comments

Comments

@Doetheman
Copy link

Doetheman commented Jul 12, 2024

Describe the bug
A clear and concise description of what the bug is.

When my team updates monitoring via the datadog api client using the calling update monitor method the MonitorUpdateRequest returns an attribute error.

datadog_api_client.exceptions.ApiAttributeError: MonitorUpdateRequest has no attribute 'restriction_policy' at ['restriction_policy']

To Reproduce
Steps to reproduce the behavior:

  1. Export monitor as a JSON
  2. Add to code base
  3. Use the datadog api to update monitoring
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Our monitors should update and not return an error when parsing the JSON.

Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 2024-07-12 at 12 17 13 PM

Environment and Versions (please complete the following information):
A clear and precise description of your setup:

Latest version of datadog api client, datadog-api-client-2.26.0

@audiolion
Copy link

Same bug

Copy link

github-actions bot commented Sep 6, 2024

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 github-actions bot added the stale label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants