Discussion/Enhancement Proposal: Higher Level API Abstraction

[Patristo]

I think it would be helpful to have a higher-level, object-based abstraction around the current API. Is this something that other people would find valuable?

Somewhat like Boto3 Service Resources for the AWS API With that, there are Waiter and Paginator objects that can handle the polling, pagination, automatic retries after rate limiting. Similarly, a heirarchy of objects and collections of child objects, which can lazy load as needed. An application no longer needs to be cluttered with polling logic.

[Patristo]

This issue was intended for me to gauge interest/the value of the proposal.

I've been working something similar internally, and was wanting to see whether it would be worth fleshing out, and seeing about open sourcing it.

[JustAShoeMaker]

I know it's been a while but seems reasonable to me, it might be a way to bring this to the next tier.

Might have to be one of those things that you build first and they will come.

[blaise-sumo]

@Patristo , @JustAShoeMaker , thanks for these suggestions. I'm relatively new at Sumo, and I have a secret plan to make this an exemplary repo. If you have suggestions or would like to review changes, please let me know. I'm blaise at sumo logic.