Clickup integrations #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClickUp Integration
- Added support for both folder less and folder based projects - Added custom properties of workspace id to each project
Fixed import statement for custom properties
Fixed import statement for custom properties
added team_id to issues in folder
- Fixed getting folders in space - Fixed username not string
Fixed data mapping problems
Fixed data mapping
Fixed assignees issues
Fixing date mapping
Made username string
Fixed unterminated if
Correcting data mapping
…cean into clickup-integrations Origin sync
- Removed unnecessary default - Replaced username with email
Refixed date
Fixed folder export error
Remapped members
This reverts commit 1d75982.
* Bumped ocean version to ^0.10.11 for argocd * Bumped ocean version to ^0.10.11 for aws * Bumped ocean version to ^0.10.11 for azure * Bumped ocean version to ^0.10.11 for azure-devops * Bumped ocean version to ^0.10.11 for datadog * Bumped ocean version to ^0.10.11 for dynatrace * Bumped ocean version to ^0.10.11 for fake-integration * Bumped ocean version to ^0.10.11 for firehydrant * Bumped ocean version to ^0.10.11 for gcp * Bumped ocean version to ^0.10.11 for gitlab * Bumped ocean version to ^0.10.11 for jenkins * Bumped ocean version to ^0.10.11 for jira * Bumped ocean version to ^0.10.11 for kafka * Bumped ocean version to ^0.10.11 for kubecost * Bumped ocean version to ^0.10.11 for launchdarkly * Bumped ocean version to ^0.10.11 for linear * Bumped ocean version to ^0.10.11 for newrelic * Bumped ocean version to ^0.10.11 for octopus * Bumped ocean version to ^0.10.11 for opencost * Bumped ocean version to ^0.10.11 for opsgenie * Bumped ocean version to ^0.10.11 for pagerduty * Bumped ocean version to ^0.10.11 for sentry * Bumped ocean version to ^0.10.11 for servicenow * Bumped ocean version to ^0.10.11 for snyk * Bumped ocean version to ^0.10.11 for sonarqube * Bumped ocean version to ^0.10.11 for statuspage * Bumped ocean version to ^0.10.11 for terraform-cloud * Bumped ocean version to ^0.10.11 for wiz
# Description What - Improved on the way the integration handles GitOps push events by using only files that have been changed in the push even rather than fetching the entire repository tree Why - Some customers were not receiving the push events in their GitLab GitOps How - ## 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) <h4> All tests should be run against the port production environment(using a testing org). </h4> ### 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 showing successful ingestion <img width="1165" alt="Screenshot 2024-09-17 at 8 03 09 PM" src="https://github.com/user-attachments/assets/b1093d31-4f85-4566-9a65-9fe75dd0114b"> entity diffs operations <img width="1127" alt="Screenshot 2024-09-17 at 8 03 26 PM" src="https://github.com/user-attachments/assets/dee6db29-28db-4ff6-80cb-96e1bfd1aa1c"> ## API Documentation Provide links to the API documentation used for this integration.
…bs#1014) # Description What - We had a bug where GitLab webhooks were disabled on restart. The disablement could also be used by GitLab when the receiving host does not meet their requirement. I updated the logic for creating webhook such that it can re-create existing webhooks when it has been disabled. Why - How - ## 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) <h4> All tests should be run against the port production environment(using a testing org). </h4> ### 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 - [x] Integration able to create all default resources from scratch - [x] Resync able to create entities - [x] Resync able to update entities - [ ] Resync able to detect and delete entities - [x] 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. - [x] If resource kind is updated, run the integration with the example data and check if the expected result is achieved - [x] 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 <img width="1106" alt="Screenshot 2024-09-13 at 5 10 08 PM" src="https://github.com/user-attachments/assets/6a5084a1-148e-4d3a-ae57-40cd42269214"> ## API Documentation [Delete Hook API](https://docs.gitlab.com/ee/api/group_webhooks.html#delete-a-group-hook) [Create Hook API ](https://docs.gitlab.com/ee/api/group_webhooks.html#add-a-group-hook) --------- Co-authored-by: Tom Tankilevitch <59158507+Tankilevitch@users.noreply.github.com>
# Description What - added logs Why - better UX How - ## 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) <h4> All tests should be run against the port production environment(using a testing org). </h4> ### 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. ## API Documentation Provide links to the API documentation used for this integration.
# Description **What** - Improved the mechanism for parallel fetching of AWS account resources. - Fixed `ExpiredTokenException` by replacing the event-based caching system with a time-dependent caching mechanism. The new approach ensures that the role is reassumed and session credentials are refreshed when 80% of the session duration has been used. **Why** - The previous event-based caching system led to the `ExpiredTokenException`, causing session credentials to expire unexpectedly. - Implementing a time-dependent caching mechanism ensures that session credentials are refreshed proactively, preventing disruptions. **How** - Replaced the resync-dependent caching system with a time-based cache that monitors the session expiry. - Added logic to reassume the role and refresh credentials once 80% of the session duration has passed, improving session reliability. ## Type of change Please leave one option from the following and delete the rest: - [x] Bug fix (non-breaking change which fixes an issue) <h4> All tests should be run against the port production environment(using a testing org). </h4> ### 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. ## API Documentation Provide links to the API documentation used for this integration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What -
Why -
How -
Type of change
Please leave one option from the following and delete the rest:
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.