[Integration][Azure DevOps] Added monorepo support

[dev-habib-nuhu]

trafficstars

Description

What - Added monorepo support to the Azure DevOps integration by implementing folder-based repository scanning:

• Implemented folder pattern processing functionality to support monorepo scanning:
• Created process_folder_patterns method to handle multiple folder patterns across repositories
• Added support for repository-specific branch mapping through FolderPattern configuration
• Implemented folder enrichment to track repository context and branch information
• Added repository folder discovery capabilities through get_repository_folders
• Implemented repository scanning with pattern matching
• Introduced FolderPattern for defining repository and path patterns
• Added repository mapping configuration to specify branches per repository

Why - -Enable users to search and retrieve folder information across multiple repositories How -

Implemented get_repository_folders() method to:

• Fetch folder structures from specific repositories
• Support path-based filtering
• Handle 404 responses for missing paths

Added generate_repositories() method to:

• Asynchronously iterate through available repositories
• Support batch processing of repositories

Implemented process_folder_patterns() to:

• Process multiple folder patterns across repositories
• Match repositories against configured patterns

Enrich folder metadata with:

• Repository information
• Branch context
• Pattern matching data
• Yield batches of matching folders asynchronously

Added unit tests

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.

API Documentation

Provide links to the API documentation used for this integration.

[aws-amplify-eu-west-1[bot]]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1631.d1ftd8v2gowp8w.amplifyapp.com