TE-4262: Updating SDK version 25.12.1#11
Merged
prashanthvarma merged 1 commit intoGraphiant-Inc:mainfrom Dec 17, 2025
Merged
Conversation
|
FWIW, here is a summary of non-backward compatible changes in the published OpenAPI spec: $ docker run --rm -t --mount type=bind,src=$PWD,dst=/data tufin/oasdiff breaking --format markdown /data/graphiant_api_docs_v25.11.1.json /data/graphiant_api_docs_v25.12.1.json# API Changelog 25.11.1 vs. 25.12.1
## PATCH /v1/account/email
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/account/info
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/account/mfa
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/account/password
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/alarm-mute/{alarmId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/apps/bandwidth
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/apps/visualization
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## DELETE /v1/auth
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/auth
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/auth
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/auth/mfa
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/auth/mfa
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/auth/mfa/types
- :warning: removed the media type 'application/json' for the response with the status '204'
## GET /v1/auth/user
- :warning: added the new 'none' enum value to the 'permissions/assetManager' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/billingAndInvoicing' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/compliance' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/developerTools' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/globalServices' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/insights' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/licensing' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/logs' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/monitoringAndTroubleshooting' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/networkConfigurations' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/orderStatus' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/reports' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/safetyAndSecurity' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/servicePolicies' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/support' response property for the response status '200'
- :warning: added the new 'none' enum value to the 'permissions/userAndTenantManagement' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/assetManager' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/billingAndInvoicing' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/compliance' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/developerTools' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/globalServices' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/insights' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/licensing' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/logs' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/monitoringAndTroubleshooting' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/networkConfigurations' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/orderStatus' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/reports' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/safetyAndSecurity' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/servicePolicies' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/support' response property for the response status '200'
- :warning: added the new 'read' enum value to the 'permissions/userAndTenantManagement' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/assetManager' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/billingAndInvoicing' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/compliance' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/developerTools' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/globalServices' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/insights' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/licensing' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/logs' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/monitoringAndTroubleshooting' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/networkConfigurations' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/orderStatus' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/reports' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/safetyAndSecurity' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/servicePolicies' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/support' response property for the response status '200'
- :warning: added the new 'read_write' enum value to the 'permissions/userAndTenantManagement' response property for the response status '200'
## DELETE /v1/device/snapshot/{snapshotId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/devices/bringup
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/devices/inventory/enterprise
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/devices/inventory/serial-num
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/devices/upgrade/cancel
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/devices/upgrade/schedule
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/devices/{deviceId}/draft
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/diagnostic/archive-delete/{archiveId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/archive-edit/{archiveId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/bgp-reset/{deviceId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/clear-arp/{deviceId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/interface-reset/{deviceId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/diagnostic/packetcapture-stop
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/diagnostic/ping-pause-resume
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/diagnostic/ping-stop/{token}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/reboot/{deviceId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/diagnostic/reset-ipsec-session/{deviceId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/enterprises
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/enterprises
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/enterprises/eula
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/enterprises/self
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/enterprises/{enterpriseId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/extranet-b2b-monitoring/peering-service/bandwidth-usage
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet-b2b-monitoring/peering-service/consumers-usage/top
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet-b2b-monitoring/peering-service/consumption-overview
- :warning: the request property 'flippedView' became required
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet-b2b-monitoring/peering-service/service-customer-list
- :warning: the request property 'id' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet-b2b-monitoring/peering-service/service-health
- :warning: the request property 'id' became required
- :warning: the request property 'isProvider' became required
## POST /v1/extranet-b2b-monitoring/peering-service/service-overtime-consumption
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet/sites-usage
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranet/sites-usage/top
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/extranets-b2b
- :warning: the request property 'policy' became required
- :warning: the request property 'policy/natPools' became required
- :warning: the request property 'policy/prefixTags/items/prefix' became required
- :warning: the request property 'policy/profiles/items/ports' became required
- :warning: the request property 'policy/profiles/items/protocol' became required
- :warning: the request property 'policy/serviceLanSegment' became required
- :warning: the request property 'policy/servicePrefixes' became required
- :warning: the request property 'policy/sites' became required
- :warning: the request property 'policy/sites/items/policerSiteLists/burstSize' became required
- :warning: the request property 'policy/sites/items/policerSiteLists/bw' became required
- :warning: the request property 'policy/sites/items/policerSites/burstSize' became required
- :warning: the request property 'policy/sites/items/policerSites/bw' became required
- :warning: the request property 'policy/type' became required
- :warning: the request property 'serviceName' became required
- :warning: the request property 'type' became required
## POST /v1/extranets-b2b-peering/consumer/{matchId}
- :warning: the request property 'id' became required
- :warning: the request property 'nat' became required
- :warning: the request property 'nat/items/prefix' became required
- :warning: the request property 'policy' became required
- :warning: the request property 'siteInformation' became required
- :warning: the request property 'siteInformation/items/policerSiteLists/burstSize' became required
- :warning: the request property 'siteInformation/items/policerSiteLists/bw' became required
- :warning: the request property 'siteInformation/items/policerSites/burstSize' became required
- :warning: the request property 'siteInformation/items/policerSites/bw' became required
## POST /v1/extranets-b2b-peering/customer
- :warning: the request property 'invite' became required
- :warning: the request property 'invite/adminEmail' became required
- :warning: the request property 'invite/maximumNumberOfSites' became required
- :warning: the request property 'name' became required
- :warning: the request property 'type' became required
## POST /v1/extranets-b2b-peering/match/service-to-customer
- :warning: the request property 'id' became required
- :warning: the request property 'service' became required
- :warning: the request property 'service/id' became required
- :warning: the request property 'service/nat' became required
- :warning: the request property 'service/nat/items/prefix' became required
- :warning: the request property 'service/servicePrefixes' became required
- :warning: the request property 'service/servicePrefixes/items/prefix' became required
## POST /v1/extranets-b2b-peering/producer
- :warning: the request property 'policy' became required
- :warning: the request property 'policy/prefixTags' became required
- :warning: the request property 'policy/prefixTags/items/prefix' became required
- :warning: the request property 'policy/serviceLanSegment' became required
- :warning: the request property 'policy/site' became required
- :warning: the request property 'policy/site/items/policerSiteLists/burstSize' became required
- :warning: the request property 'policy/site/items/policerSiteLists/bw' became required
- :warning: the request property 'policy/site/items/policerSites/burstSize' became required
- :warning: the request property 'policy/site/items/policerSites/bw' became required
- :warning: the request property 'policy/type' became required
- :warning: the request property 'type' became required
## POST /v1/extranets-b2b/consumer
- :warning: the request property 'policy/items/rules/items/servicePrefix' became required
- :warning: the request property 'siteInformation/items/policerSiteLists/burstSize' became required
- :warning: the request property 'siteInformation/items/policerSiteLists/bw' became required
- :warning: the request property 'siteInformation/items/policerSites/burstSize' became required
- :warning: the request property 'siteInformation/items/policerSites/bw' became required
## PUT /v1/extranets-b2b/{id}
- :warning: the request property 'policy' became required
- :warning: the request property 'policy/natPools' became required
- :warning: the request property 'policy/prefixTags/items/prefix' became required
- :warning: the request property 'policy/profiles/items/ports' became required
- :warning: the request property 'policy/profiles/items/protocol' became required
- :warning: the request property 'policy/serviceLanSegment' became required
- :warning: the request property 'policy/servicePrefixes' became required
- :warning: the request property 'policy/sites' became required
- :warning: the request property 'policy/sites/items/policerSiteLists/burstSize' became required
- :warning: the request property 'policy/sites/items/policerSiteLists/bw' became required
- :warning: the request property 'policy/sites/items/policerSites/burstSize' became required
- :warning: the request property 'policy/sites/items/policerSites/bw' became required
- :warning: the request property 'policy/type' became required
## POST /v1/extranets-b2b/{id}/customer/
- :warning: the request property 'invites' became required
- :warning: the request property 'invites/items/adminEmail' became required
- :warning: the request property 'invites/items/consumerBurstSize' became required
- :warning: the request property 'invites/items/consumerBwSite' became required
- :warning: the request property 'invites/items/enterpriseId' became required
- :warning: the request property 'invites/items/maximumSiteCount' became required
## POST /v1/flows/flow-table
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/flows/topology
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## DELETE /v1/global/lan-segments/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/global/site-lists/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/groups
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/groups/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/groups/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/groups/{id}/enterprises
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/groups/{id}/enterprises/{enterpriseId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/groups/{id}/members
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/groups/{id}/members/delete
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/groups/{id}/members/{memberId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/monitoring/circuits/bandwidth
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/monitoring/circuits/incidents
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/monitoring/circuits/summary
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/monitoring/circuits/utilization
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v1/monitoring/circuits/visualization
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## DELETE /v1/onboarding/cloudinit
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/policy/prefix-sets/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/portal/private
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/portal/private/register
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v1/portal/private/sync
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/sites/{siteId}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/software/auto-upgrade/default
- :warning: removed the media type 'application/json' for the response with the status '204'
## PUT /v1/users
- :warning: removed the media type 'application/json' for the response with the status '204'
## DELETE /v1/users/{id}
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/users/{id}/verify
- :warning: removed the media type 'application/json' for the response with the status '204'
## PATCH /v1/{id}/password/recover
- :warning: removed the media type 'application/json' for the response with the status '204'
## POST /v2/extranet/consumers-usage/top
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v2/extranet/lan-segments-usage/top
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v2/extranet/service-overtime-consumption
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v2/extranet/sites-consumption-overview
- :warning: the request property 'flippedView' became required
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v2/extranet/sites-usage
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## POST /v2/extranet/total-usage
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
- :warning: the request property 'timeWindow' became required
- :warning: the request property 'timeWindow/bucketSizeSec' became required
## GET /v2/monitoring/extranet/edge-status
- :warning: added the new required 'query' request parameter 'id'
- :warning: added the new required 'query' request parameter 'isProvider'
## POST /v2/monitoring/extranet/log-details
- :warning: the request property 'id' became required
- :warning: the request property 'isB2B' became required
- :warning: the request property 'isProvider' became required
## GET /v2/monitoring/extranet/service-status
- :warning: added the new required 'query' request parameter 'id'
- :warning: added the new required 'query' request parameter 'isProvider'
## GET /v2/monitoring/extranet/service-status/details
- :warning: added the new required 'query' request parameter 'id'
- :warning: added the new required 'query' request parameter 'isProvider'
## GET /v2/monitoring/extranet/site-status
- :warning: added the new required 'query' request parameter 'id'
- :warning: added the new required 'query' request parameter 'isProvider'
## GET /v2/monitoring/extranet/status-details
- :warning: added the new required 'query' request parameter 'id'
- :warning: added the new required 'query' request parameter 'isProvider'
- :warning: added the new required 'query' request parameter 'serverAddress'
- :warning: added the new required 'query' request parameter 'siteId' |
|
As well checking for non-backward compatible changes the oasdiff tool can generate a full changelog: which is also available as a GitHub action: https://github.com/oasdiff/oasdiff-action?tab=readme-ov-file#generate-a-changelog, that could perhaps be included in the release or a pull-request workflow. (though from a read of oasdiff/oasdiff-action#55 (comment) it appears the action doesn't make it easy to get before/after copies of the spec file to compare 🤷 ) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.