feat: extract v2 endpoints with v1.0/v1.5 parity #1096
Draft
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.
Proposed changes
This PR introduces a new PoC script (
scripts/endpoint-parity.js) that analyzes and identifies endpoint parity between the legacy v1/v1.5 APIs and the v2 API, specifically focusing on endpoints with upcoming sunset dates.v1.0endpoints map 1-to-1 withv2 2023-01-01endpointsv1.5endpoints map 1-to-1 withv2 2023-02-01endpointsJira ticket: CLOUDP-372985
Closes #[issue number]
Checklist
Changes to Spectral
Further comments