microsoftgraph / microsoftgraph/msgraph-sdk-python
Long running operations Support
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
In Azure SDK/API as an example,
Long running operations are performed in the following flow?
- A URL is returned that can be used to retrieve the result of the operation once completed.
- The URL can be used to monitor the status of the operation, at regular intervals until it is completed.
- Optionally a callback URL is availed that can be used to get notification once a long running operation is completed.
Technically, this looks like polling and a callback URL.
Do we have a spec on this for Graph SDKs @baywet @andrueastman @darrelmiller @ddyett @Ndiritu @samwelkanda
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's Azure SDK/API example and the Graph SDK references to determine whether long-running operations, polling, and callback URLs have an existing specification. Done would require an agreed Graph SDK specification or a clearly scoped implementation request; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100