[GitHub Bot] Generated python SDK - #168
Conversation
☂️ Python Coverage
Overall Coverage
New Files
Modified Files
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b300d0ccbc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| from thousandeyes_sdk.event_detection.models.domain_event_grouping import DomainEventGrouping | ||
| from thousandeyes_sdk.event_detection.models.error import Error | ||
| from thousandeyes_sdk.event_detection.models.event import Event | ||
| from thousandeyes_sdk.event_detection.models.event_affected_agent_type import EventAffectedAgentType |
There was a problem hiding this comment.
Preserve the previous affected-agent enum imports
When existing consumers upgrade, imports such as from thousandeyes_sdk.event_detection import CloudEnterpriseAgentType and from thousandeyes_sdk.event_detection.models.cloud_enterprise_agent_type import CloudEnterpriseAgentType now fail because this commit removes both the public export and module while replacing the enum with a compatible superset. Retain a deprecated alias/module for CloudEnterpriseAgentType so this API schema rename does not become an avoidable SDK-breaking change.
Useful? React with 👍 / 👎.
| end_date: Annotated[Optional[datetime], Field(description="Defaults to current time the request is made. Use with the `startDate` parameter. Include the complete time (hours, minutes, and seconds) in UTC time zone, following the ISO 8601 date-time format. See the example for reference. Please note that this parameter can't be used with `window`.")] = None, | ||
| max: Annotated[Optional[StrictInt], Field(description="(Optional) Maximum number of objects to return.")] = None, | ||
| cursor: Annotated[Optional[StrictStr], Field(description="(Optional) Opaque cursor used for pagination. Clients should use `next` value from `_links` instead of this parameter.")] = None, | ||
| ongoing: Annotated[Optional[StrictBool], Field(description="When set to `true`, only ongoing (active) events whose start date is within the specified time window are included in the response. When set to `false`, ongoing events are excluded from the response. If not set, both ongoing and concluded events appear in the response.")] = None, |
There was a problem hiding this comment.
Avoid shifting existing positional transport arguments
When an existing caller passes _request_timeout or a later transport option positionally, inserting ongoing before those parameters changes the argument binding after upgrade; for example, a previously valid seventh argument of 30 is now validated as ongoing and raises a Pydantic boolean validation error instead of setting the timeout. Preserve the prior positional slots, such as by making the new option keyword-only, across get_events and its companion variants.
Useful? React with 👍 / 👎.
No description provided.