Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Integration][Azure] Enhanced API Version Consistency in Resource Man…
…agement Client (#1321) # Description What - Updated the `list_resources` function to set both `_config.api_version` and `_api_version` in the `ResourceManagementClient.resources` object. Why - The `_config.api_version` alone was insufficient in ensuring consistent behavior across paginated responses and API interactions as list method defaults to the `_api_version` for 2nd iteration and beyond during iteration through paginated response. By also setting `_api_version`, the resource client uses the specified version throughout its operations, improving reliability and consistency when querying Azure resources. How - Patched default value for `resources_client.resources._api_version` ## 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.
- Loading branch information