acuarica
commented
7 months ago Is there a way to disable the related endpoints in the Swagger UI when SERVER_CREATE2_VERIFICATION if not enabled?
This is because otherwise these endpoints return 404 but with an HTML format instead of JSON. This in turn looks like a configuration error. For instance this is the response from the /verify/create2 endpoint
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot POST /verify/create2</pre>
</body>
</html>This is how it's seen in the Swagger API
Description:
This brings changes in the ui and in the server:
In the UI, Create2 verification will only be available when the following is added to
config.json:"CREATE2_VERIFICATION": trueNote: When Create2 is activated, the TOKEN parameter will no longer be required in the UI since it does not seem to be needed and is quite confusing.In the server, the API endpoints related to Create2 support will be exposed only if the following environment variable is defined:
SERVER_CREATE2_VERIFICATION=true