`*_with_http_info` methods no longer exist breaking Pagination Helpers

[nickbotica]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  Before submitting a bug report, we ask that you first search existing issues and pull requests to see if someone else may have experienced the same issue or may have already submitted a fix for it.

Python Version & Okta SDK Version(s)

Python v3.11.11
okta 3.4.2

Affected Class/Method(s)

*_with_http_info, e.g. okta.api.user_api.list_users_with_http_info

Customer Information

Organization Name:
Paid Customer: no

Code Snippet

# From the README example
from okta.client import Client as OktaClient
from okta import paginate_all

async def fetch_all_users(okta_client):
    """Fetch all users automatically"""
    all_users = []

    # Automatically paginate through all users
    async for user in paginate_all(
        okta_client.list_users_with_http_info,
        limit=200  # Items per page
    ):
        all_users.append(user)
        print(f"User: {user.profile.email}")

    return all_users

Debug Output / Traceback

'Client' object has no attribute 'list_users_with_http_info'

Expected Behavior

Based on the README documentation, the method should exist and provide an easy way to paginate results.

Actual Behavior

The method doesn't exist, in fact no _with_http_info methods exist. This happened as part of the v3.1.0 PR:

v3.0.0...v3.1.0#diff-2be9dde36400fcb4b16e1cae532c588187ca09734ea73827073ff04d27bf4d41L9947

I believe this is not intentional as the PR title references 'Pagination Support' and the second commit adds the current Pagination examples in the README.

Steps to reproduce

1. Run the code snippet provided above.

References

No response