-
Notifications
You must be signed in to change notification settings - Fork 61
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][PagerDuty] - Default Resources Enhancements #1182
Conversation
- Improved on the integration default resources for PagerDuty incidents kind | ||
- Added blueprint and mapping for PagerDuty users | ||
- Added logs to track the HTTP requests made to PagerDuty API | ||
- Added a generic resync event handler to allow the integration to bring any valid resource from PagerDuty |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which ones are expected to work? can we make sure we have a proper log on when we aren't able to sync data for the passed "generic" kind?
@ocean.on_resync() | ||
async def on_global_resync(kind: str) -> ASYNC_GENERATOR_RESYNC_TYPE: | ||
|
||
if kind in OBJECTS_WITH_SPECIAL_HANDLING: | ||
logger.info(f"Kind {kind} has a special handling. Skipping...") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you document expected resources that can be passed here? like users
etc..
…://github.com/port-labs/ocean into PORT-11473-pagerduty-integration-enhancements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
What - Added enhancements to the integration default resources as well as the integration itself.
Why - Rethinking the way we map data from PagerDuty and the need to improve on the overall user experiences
How - By undertaking the following:
Type of change
Please leave one option from the following and delete the rest:
All tests should be run against the port production environment(using a testing org).
Core testing checklist
Integration testing checklist
examples
folder in the integration directory.Preflight checklist
Screenshots
Include screenshots from your environment showing how the resources of the integration will look.
API Documentation
Provide links to the API documentation used for this integration.