-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert v2 API test fragments to v3 #10843
Comments
@htuch i would like to work on this as part of beginner in community. |
@htuch i read #10644 and found that changes were made in docs/root directory from V2 API ref to V3 API wherever applicable . from the problem statement for this issue do i need to make similar changes (in json and ymal) inside directory structure ../test/ , please correct if i am wrong. |
@ankatare yep, that's the goal. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
/no stalest |
Commit Message: changes in test files for "Convert v2 API test fragments to v3" Additional Description: file changes in test/common/upstream/ Testing: format test and integration test Progress toward #10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com>
Risk Level:Low Testing: integration and format testing Part of #10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com>
This shouldn't be closed. |
@alyssawilk thanks for this suggestion i will tc it from next time. |
@alyssawilk would you check this PR#12113. hope now it is fine as per your suggestion ? |
V2 to V3 changes for parseFoofromV2json : Risk Level: NA Testing: unit and format Docs Changes: NA Part of #10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com>
What's super weird is that I manually modify the commit messages and switch them from "Fixes #123456" to "Part of #123456" when I merge. GitHub still seems to close them out. |
Commit Message: changes for http and access_log folders Risk Level:NA Testing: Unit and format testing Docs Changes: NA part of #10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com>
V2 to V3 changes related to test/commom/router/ directory. Risk Level: Low Testing: unit, integration and format testing Docs Changes: NA Relates to envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: Kevin Baichoo <kbaichoo@google.com>
V2 to V3 changes for parseFoofromV2json : Risk Level: NA Testing: unit and format Docs Changes: NA Part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: Kevin Baichoo <kbaichoo@google.com>
Commit Message: changes for http and access_log folders Risk Level:NA Testing: Unit and format testing Docs Changes: NA part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: Kevin Baichoo <kbaichoo@google.com>
Risk Level:Low Testing: integration and format testing Part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
v2 to v3 fragment changes for parseClusterFromV2Yaml Risk Level: low Testing: unit, format and integration test Docs Changes: NA Release Notes: Part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
…2072) v2 to v3 changes for function constructConfigFromV2Yaml under file "test/common/tcp_proxy/tcp_proxy_test.cc" Additional Description: This PR is duplicate of PR envoyproxy#11923 Part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
V2 to V3 changes related to test/commom/router/ directory. Risk Level: Low Testing: unit, integration and format testing Docs Changes: NA Relates to envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
V2 to V3 changes for parseFoofromV2json : Risk Level: NA Testing: unit and format Docs Changes: NA Part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
Commit Message: changes for http and access_log folders Risk Level:NA Testing: Unit and format testing Docs Changes: NA part of envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
…st/.. (envoyproxy#12058) Commit Message: v2 to v3 fragment changes for extension and server directory test cases. Risk Level: Low Testing: unit and format Fixes envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com>
…st/.. (envoyproxy#12058) Commit Message: v2 to v3 fragment changes for extension and server directory test cases. Risk Level: Low Testing: unit and format Fixes envoyproxy#10843 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Signed-off-by: chaoqinli <chaoqinli@google.com>
While all programatically constructed test configs will be v3 (via API boosting rewriting), there are still v2 JSON/YAML fragments in test code. Many of these will "just work" as v3, but some may have v2 features that will have them treated as v2. This becomes confusing when they are extended by developers who want to model v3 features.
These need to be audited and updated as appropriate. Also, the names of methods such as
parseAccessLogFromV2Yaml
should be updated to reflect v3 when operating on fragments that should be v3.This is somewhat similar to the work done by @dmitri-d for examples in #10644 as part of #9735.
CC @alyssawilk
The text was updated successfully, but these errors were encountered: