@dynatrace-sdk/client-classic-environment-v2 7.0.0 → 9.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/CHANGELOG.md +46 -15
  2. package/README.md +3291 -3134
  3. package/cjs/index.js +231 -23
  4. package/dynatrace-metadata.json +2 -2
  5. package/esm/index.js +231 -23
  6. package/package.json +1 -1
  7. package/types/index.d.ts +1158 -52
package/CHANGELOG.md CHANGED
@@ -2,31 +2,62 @@
2
2
 
3
3
  @dynatrace-sdk/client-classic-environment-v2
4
4
 
5
+ ## 9.0.0
6
+
7
+ ### Major Changes
8
+ - BREAKING: `SyntheticLocationsNodesAndConfigurationClient.updateConfiguration` now returns `Promise<void>` because the endpoint returns HTTP 204 without a response body. Do not consume the resolved `SyntheticConfigDto`.
9
+ - BREAKING: `SyntheticConfigDto.maintenanceWindowsExcludedFromAvailability` is now required. Include this field in every `updateConfiguration` request.
10
+
11
+ ### Minor Changes
12
+ - Add optional `monitorCrossOriginFrames` to `SyntheticBrowserMonitorConfigurationDto`.
13
+ - Add `asHistogram` to metric descriptor transformations.
14
+ - Deprecate the API-token operations on `accessTokensApiTokensClient`.
15
+
16
+ ## 8.0.0
17
+
18
+ ### Breaking Changes
19
+
20
+ - Made `securityContext` required in `SecurityContextDtoImpl`. As this is the request body of `monitoredEntitiesClient.setSecurityContext`, callers must now always provide `body.securityContext` (previously optional) — pass `securityContext: []` to clear it or the desired management-zone IDs to set it.
21
+
22
+ ### Features
23
+
24
+ - Added `getRotationStatus` method to `AccessTokensTenantTokensClient` for querying tenant token rotation status. Added `TenantTokenRotationStatus` model and `TenantTokenRotationStatusStatus` enum (`ACTIVE`, `INACTIVE`).
25
+ - Added `minActiveGateCount`, `maxActiveGateCount`, and `nodeSize` fields to `PrivateSyntheticLocation`. Added `PrivateSyntheticLocationNodeSize` enum (`XS`, `S`, `M`, `UNSUPPORTED`).
26
+ - Added `sql-extension-executor` value to `ContainerImageComponent.type` and the `ContainerImageComponentType` enum.
27
+ - Added `LIMITED_BY_SERVICE_DETECTION_V2` value to `AssessmentAccuracyDetails.reducedReasons` and the `AssessmentAccuracyDetailsReducedReasonsItem` enum.
28
+ - Made `entityId` and `type` required in `SyntheticMonitorSummaryDto` (response-only type).
29
+ - Updated JSDoc with example, minimum, and default fields. (APPDEV-16816)
30
+
31
+ ### Deprecations
32
+
33
+ - Deprecated `getActiveGateGroups` in `ActiveGatesActiveGateGroupsClient`.
34
+ - Deprecated `getAllActiveGates` and `getOneActiveGateById` in `ActiveGatesClient`.
35
+
5
36
  ## 7.0.0
6
37
 
7
38
  ### New capabilities
8
39
 
9
- * Added support for *HTTP Synthetic Monitors* in the Classic Environment V2 SDK. New request and response models now support the HTTP monitor type.
10
- * Added new AdaptiveTrafficManagementClient.
11
- * Added new FleetManagementContainerImagesClient.
40
+ - Added support for _HTTP Synthetic Monitors_ in the Classic Environment V2 SDK. New request and response models now support the HTTP monitor type.
41
+ - Added new AdaptiveTrafficManagementClient.
42
+ - Added new FleetManagementContainerImagesClient.
12
43
 
13
44
  ### API contract changes impacting UI/AI integrations
14
45
 
15
- * Removed securityContext from Browser, HTTP, and Multi-Protocol monitor request/response models.
16
- * UI forms, state mapping, validation logic, and AI workflows relying on this field must be updated.
17
- * Synthetic monitor response models were extended to include the HTTP monitor type.
18
- * Type guards, monitor filtering, monitor creation flows, and monitor-specific UI rendering may require updates.
19
- * SyntheticMonitorSummaryDto no longer contains the THIRD_PARTY monitor type.
20
- * Consumers should review monitor-type handling logic, filters, analytics, and reporting logic.
21
- * Asset catalog models now support the DOCUMENT_SCREEN asset type.
22
- * Asset type selectors, renderers, and AI classification workflows should support the new value.
23
- * API token scope definitions now include openpipeline.events_smartscape.
24
- * Permission UIs, scope validation, and access-management flows may require updates.
46
+ - Removed securityContext from Browser, HTTP, and Multi-Protocol monitor request/response models.
47
+ - UI forms, state mapping, validation logic, and AI workflows relying on this field must be updated.
48
+ - Synthetic monitor response models were extended to include the HTTP monitor type.
49
+ - Type guards, monitor filtering, monitor creation flows, and monitor-specific UI rendering may require updates.
50
+ - SyntheticMonitorSummaryDto no longer contains the THIRD_PARTY monitor type.
51
+ - Consumers should review monitor-type handling logic, filters, analytics, and reporting logic.
52
+ - Asset catalog models now support the DOCUMENT_SCREEN asset type.
53
+ - Asset type selectors, renderers, and AI classification workflows should support the new value.
54
+ - API token scope definitions now include openpipeline.events_smartscape.
55
+ - Permission UIs, scope validation, and access-management flows may require updates.
25
56
 
26
57
  ### ActiveGate model changes
27
58
 
28
- * targetVersion and updateWindows were removed from ActiveGate auto-update configuration models.
29
- * Introduced dedicated UpdateWindow and UpdateWindowsConfig models.
59
+ - targetVersion and updateWindows were removed from ActiveGate auto-update configuration models.
60
+ - Introduced dedicated UpdateWindow and UpdateWindowsConfig models.
30
61
 
31
62
  ## 6.1.0
32
63