🌊 Ocean 🌊 is an innovative solution developed by Port to seamlessly integrate various third-party systems with our developer portal product, empowering engineers to effortlessly prioritize key features and streamline the integration process.
What -
Updated the Snyk Integration to accept a list of organization IDs instead of a single ID. This change allows users to specify multiple organizations when setting up the integration, enabling more granular control over which organizations' data is ingested.
Why -
Previously, the Snyk Integration only allowed the specification of a single organization ID, which posed a limitation for users who needed to fetch data from multiple organizations within their Snyk account. This limitation led to errors when users attempted to input a comma-separated list of organization IDs. By allowing a list of organization IDs, the integration becomes more flexible, accommodating the needs of users managing multiple organizations, especially when dealing with sensitive data where selective ingestion is required.
How -
The integration code was modified to accept and process a comma-separated list of organization IDs. The system now iterates through each organization ID provided, fetching data accordingly. This update maintains backward compatibility, ensuring that the integration will continue to function as expected for users who provide a single organization ID. Additionally, the description of the organizationId input parameter has been updated to reflect this new functionality.
Type of change
[x] New feature (non-breaking change which adds functionality)
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
[x] Integration able to create all default resources from scratch
[x] Resync able to create entities
[x] Resync able to update entities
[x] 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.
[ ] 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
Description
What -
Updated the Snyk Integration to accept a list of organization IDs instead of a single ID. This change allows users to specify multiple organizations when setting up the integration, enabling more granular control over which organizations' data is ingested.
Why -
Previously, the Snyk Integration only allowed the specification of a single organization ID, which posed a limitation for users who needed to fetch data from multiple organizations within their Snyk account. This limitation led to errors when users attempted to input a comma-separated list of organization IDs. By allowing a list of organization IDs, the integration becomes more flexible, accommodating the needs of users managing multiple organizations, especially when dealing with sensitive data where selective ingestion is required.
How -
The integration code was modified to accept and process a comma-separated list of organization IDs. The system now iterates through each organization ID provided, fetching data accordingly. This update maintains backward compatibility, ensuring that the integration will continue to function as expected for users who provide a single organization ID. Additionally, the description of the
organizationIdinput parameter has been updated to reflect this new functionality.Type of change
All tests should be run against the port production environment(using a testing org).
Core testing checklist
Integration testing checklist
examplesfolder 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.