You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The licensing api method get_counted_feature_stats has two issues:
The method always returns None. This is due to a 200 OK response code coming back from API endpoint instead of the 202 Accepted response expected by the method. Its of note that the Controllers (v6.0 build 14216) swagger API spec doesn't document a 200 response, (which would explain why the openapi-generator didn't include it in the code).
The 200 OK response data doesn't fully match the AsyncOperationResponse schema - it's missing a result_url field. This causes a validation error if the response data is assigned to the AsyncOperationResponse class.
Steps to Reproduce:
iimport cyperf
from cyperf.models.async_operation_response import AsyncOperationResponse
from cyperf.rest import ApiException
from pprint import pprint
# Defining the host is optional and defaults to http://localhost
# See configuration.py for a list of all supported configuration parameters.
configuration = cyperf.Configuration(
host = "https://url_here",
username="user",
password="pass",
refresh_token=None
)
configuration.verify_ssl = False
with cyperf.ApiClient(configuration) as api_client:
api_instance = cyperf.LicensingApi(api_client)
try:
api_response = api_instance.get_counted_feature_stats()
print("The response of LicensingApi->get_counted_feature_stats:\n")
pprint(api_response)
except Exception as e:
print("Exception when calling LicensingApi->get_counted_feature_stats: %s\n" % e)
Thank you for reporting this! It should be fixed in the latest build available in PyPI, and in the latest code here. We added support for the 200 OK response as an option in the generated code here, and made the result_url field optional, as it should have been.
Unfortunately we can't address the issues in the OpenAPI spec served by CyPerf Controller v6.0, but we will make sure that future releases of CyPerf controller will include the right information in the API spec.
Activity
tsimionescu commentedon Sep 22, 2025
Thank you for reporting this! It should be fixed in the latest build available in PyPI, and in the latest code here. We added support for the 200 OK response as an option in the generated code here, and made the
result_urlfield optional, as it should have been.Unfortunately we can't address the issues in the OpenAPI spec served by CyPerf Controller v6.0, but we will make sure that future releases of CyPerf controller will include the right information in the API spec.