added usage_type attribute to policy ticket details

[pranjal-astuto]

Summary by CodeRabbit

• New Features

  • Introduced new classes: FeatureIntegrationStatus, TimeFilter, and FormattedTicketActivity.
  • Enhanced GenerateSQLResponse with additional fields for detailed reasoning.
  • Improved filtering options with the new TimeFilter class.
  • Expanded TenantPolicy to track feature integration status.

• Improvements

  • Updated field types for better type safety in GetMetricsAvailabilityForResourceRequest.
  • Added a field to UpdateSavedViewResponse to indicate system-defined views.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces significant changes to the onelens_backend_client_v2/models.py file, including the addition of new classes (FeatureIntegrationStatus, TimeFilter, FormattedTicketActivity) and updates to existing classes. Noteworthy modifications include the introduction of new fields in the GenerateSQLResponse, UpdateSavedViewResponse, and TenantPolicy classes, as well as a change in the type of resource_ids in the GetMetricsAvailabilityForResourceRequest class. Several classes have been removed, indicating a restructuring of the data models.

Changes

File Path	Change Summary
onelens_backend_client_v2/models.py	- New classes: FeatureIntegrationStatus, TimeFilter, FormattedTicketActivity
	- Updated GenerateSQLResponse: added fields chain_of_thought: str, reflection: str
	- Updated GetMetricsAvailabilityForResourceRequest: changed resource_ids type from List[str] to List[UUID]
	- Updated UpdateSavedViewResponse: added field is_system_defined: Optional[bool]
	- Updated TenantPolicy: added field integration_status: FeatureIntegrationStatus
	- Removed classes: DailyFormattedActivities, GetFormattedTicketActivitiesResponse
	- Reintroduced FormattedTicketActivity with new structure including details_metadata field

Possibly related PRs

• Updated policy model #43: The changes in the TenantPolicy class in both PRs involve the addition of new fields, indicating a related restructuring of policy models in onelens_backend_client_v2/models.py.

Suggested reviewers

• kaushikkishore
• sidpan1

🐇 In the meadow, changes bloom,
New classes rise, dispelling gloom.
Fields added, some now gone,
A fresh new structure, we move on!
With integration statuses bright,
Our models shine, a joyful sight! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ee7e7b1 and 863465c.

📒 Files selected for processing (1)

• onelens_backend_client_v2/models.py (21 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.