Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unnecessary validation step before retrieving or deploying API artifacts #3530

Open
shavinsenadheera opened this issue Jan 20, 2025 · 0 comments
Open

Unnecessary validation step before retrieving or deploying API artifacts #3530

shavinsenadheera opened this issue Jan 20, 2025 · 0 comments
Labels
Type/Improvement

Comments

@shavinsenadheera
Copy link

Description

If APIs defined in the Swagger reference external APIs for data retrieval, when invoking the /internal/data/v1 API, the Swagger definition is being revalidated during runtime while we are invoking this internal/data/v1. Because of this separate validation step before retrieving or deploying API artifacts, this additional validation might be unnecessary and is causing performance issues.

Steps to Reproduce

N/A

Version

4.2.0

Environment Details (with versions)

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type/Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shavinsenadheera