You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Integration][Azure] Enhanced API Version Consistency in Resource Management 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.
Copy file name to clipboardExpand all lines: integrations/azure/CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
<!-- towncrier release notes start -->
9
9
10
+
0.1.126 (2025-01-14)
11
+
12
+
### Bug Fixes
13
+
14
+
- Fixed the listing of azure subscription resource to use the latest API version `(2023-07-01)` when building url for the next page during paginated response iterations
0 commit comments