We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In InLong-Manager module, the /openapi/dataproxy/getConfig got abnormal status result,
it should got result with business status = 130, that is, config successful.
Now the interface got result with all business status = 130.
Accessing by browser:
http://${inlong_manager_ip}/api/inlong/manager/doc.html#/default/DataProxy%20Config/getConfigUsingGET
InLong version: 0.9.0
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Expected behavior
In InLong-Manager module, the /openapi/dataproxy/getConfig got abnormal status result,
it should got result with business status = 130, that is, config successful.
Actual behavior
Now the interface got result with all business status = 130.
Steps to reproduce
Accessing by browser:
http://${inlong_manager_ip}/api/inlong/manager/doc.html#/default/DataProxy%20Config/getConfigUsingGET
System configuration
InLong version: 0.9.0
The text was updated successfully, but these errors were encountered: