Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove the legacy v2 API entry from api-paste.ini
The api sample tests and functional tests already stopped to run against with legacy v2 API. This patch removes the legacy V2 API entry from api-paste.ini, it stops user from using legacy V2 API. This patch also adds deprecated report in pipeline factory method to notice the user update their api-paste.ini after upgrade code. Partially implements blueprint remove-legacy-v2-api-code Change-Id: I1476b2e364032d7c98f71df0cd61f1d1c19e005d
- Loading branch information
Showing
4 changed files
with
25 additions
and
54 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
10 changes: 10 additions & 0 deletions
10
releasenotes/notes/remove-legacy-v2-api-7ac6d74edaedf011.yaml
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
--- | ||
upgrade: | ||
- The legacy v2 API code was deprecated since Liberty release. The legacy | ||
v2 API code was removed in Newton release. We suggest that user should | ||
move to v2.1 API which compatible v2 API with more restrict input | ||
validation and microversions support. If user is still looking for v2 | ||
compatible API before switch to v2.1 API, user can use v2.1 API code as | ||
v2 API compatible mode. That compatible mode is closer to v2 API | ||
behaviour which is v2 API compatible without restrict input validation | ||
and microversions support. |