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

[Integration][Sentry] - Add Users and Teams #1229

Merged
merged 11 commits into from
Dec 18, 2024

Conversation

PeyGis
Copy link
Contributor

@PeyGis PeyGis commented Dec 12, 2024

Description

What - Added sentry users and teams

Why - For improved data model

How - Added sentryUser and sentryTeam blueprint. And added a relation between issue and user

Type of change

Please leave one option from the following and delete the rest:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • New Integration (non-breaking change which adds a new integration)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Non-breaking change (fix of existing functionality that will not change current behavior)
  • Documentation (added/updated documentation)

All tests should be run against the port production environment(using a testing org).

Core testing checklist

  • Integration able to create all default resources from scratch
  • Resync finishes successfully
  • Resync able to create entities
  • Resync able to update entities
  • Resync able to detect and delete entities
  • Scheduled resync able to abort existing resync and start a new one
  • Tested with at least 2 integrations from scratch
  • Tested with Kafka and Polling event listeners
  • Tested deletion of entities that don't pass the selector

Integration testing checklist

  • Integration able to create all default resources from scratch
  • Resync able to create entities
  • Resync able to update entities
  • Resync able to detect and delete entities
  • Resync finishes successfully
  • If new resource kind is added or updated in the integration, add example raw data, mapping and expected result to the examples folder in the integration directory.
  • If resource kind is updated, run the integration with the example data and check if the expected result is achieved
  • If new resource kind is added or updated, validate that live-events for that resource are working as expected
  • Docs PR link here

Preflight checklist

  • Handled rate limiting
  • Handled pagination
  • Implemented the code in async
  • Support Multi account

Screenshots

Include screenshots from your environment showing how the resources of the integration will look.

Screenshot 2024-12-12 at 7 40 42 PM Screenshot 2024-12-12 at 7 41 03 PM

API Documentation

Users
Teams
Team Members

@PeyGis PeyGis requested a review from a team as a code owner December 12, 2024 19:40
@github-actions github-actions bot added size/L and removed size/M labels Dec 13, 2024
Copy link
Member

@matan84 matan84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some minor comments

integrations/sentry/.port/resources/blueprints.json Outdated Show resolved Hide resolved
integrations/sentry/.port/spec.yaml Show resolved Hide resolved
integrations/sentry/clients/sentry.py Show resolved Hide resolved
Comment on lines +31 to +37
"enum": [
"member",
"admin",
"owner",
"manager",
"biling"
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is that something static by sentry or can be adjusted by each organization?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is static from the API and consistent with the Sentry UI

):
yield teams

@cache_iterator_result()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why you need to cache this?

@@ -242,3 +242,36 @@ async def get_projects_tags_from_projects(
if project_tags_batch:
project_tags.append(project_tags_batch)
return flatten_list(project_tags)

@cache_iterator_result()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here?

Comment on lines 37 to 39
async def fetch_team_members(team_slug: str) -> list[dict[str, Any]]:
return await sentry_client.get_team_members(team_slug)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why this isn't a client method? ideally we shouldn't declare a method inside another method

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rephrase? I didn't understand the question

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feels redundant method I think

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it doesn't add anything specific

Copy link
Contributor

@Tankilevitch Tankilevitch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@matan84 matan84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PeyGis PeyGis merged commit 6b44ba5 into main Dec 18, 2024
18 checks passed
@PeyGis PeyGis deleted the PORT-11840-sentry-integration-enhancements branch December 18, 2024 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants