-
Notifications
You must be signed in to change notification settings - Fork 16
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
EntityV3MetadataOwner model misaligned with API expectations and schema registry #1859
Comments
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:
|
This is still an issue. The model here is incorrect: https://github.com/DataDog/datadog-api-client-typescript/blob/master/packages/datadog-api-client-v2/models/EntityV3MetadataOwner.ts |
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:
|
Should be resolved by https://github.com/DataDog/datadog-api-spec/pull/3529 |
Describe the bug
The definition of the
EntityV3MetadataOwner
model is wrong and leads to erroneous API calls when using this library.The DD schema repository recently fixed this issue and now correctly reflects what the API expects, but this library does not. I'm guessing someone just needs to re-compile the models?
To Reproduce
Steps to reproduce the behavior:
EntityV3MetadataOwner
model (for example,SoftwareCatalogApi.upsertCatalogEntity()
)Expected behavior
Library expects the
owner
property of the V3EntityMetadata to be a string, not an object.Screenshots
Environment and Versions (please complete the following information):
v1.29.0 of this library
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: