Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable resources to participate in progress reporting during config execution #46

Open
SteveL-MSFT opened this issue Mar 29, 2023 · 2 comments
Assignees
Labels
Issue-Enhancement The issue is a feature or idea
Milestone

Comments

@SteveL-MSFT
Copy link
Member

Summary of the new feature / enhancement

As resources get executed, need progress returned as JSON for agents to display. Consider how child processes can participate including resources.

Proposed technical implementation details (optional)

No response

@SteveL-MSFT SteveL-MSFT added the Issue-Enhancement The issue is a feature or idea label Mar 29, 2023
@anmenaga
Copy link
Collaborator

anmenaga commented Jun 28, 2023

The mechanism for reporting progress will be similar to verbose messages - #89
In human-readable mode - just a text in stdout.
In machine-readable mode - a JSON structure returned in the stderr stream that has a string operation name and an integer [0;100] that shows completion percent; the same interface will be used to report progress from resources/resource providers to dsc.exe

@anmenaga
Copy link
Collaborator

To put more context to this.
The main work item to enable progress reporting (as well as streaming results from a resource in real-time without waiting until it completes the operation) is actually to switch resource execution from synchronous to async.
I did initial implementation of it using tokio runtime.

@SteveL-MSFT SteveL-MSFT changed the title Enable progress reports during config execution Enable resources to participate in progress reporting during config execution May 29, 2024
@SteveL-MSFT SteveL-MSFT modified the milestones: 3.0-RC, Post-3.0 May 29, 2024
@SteveL-MSFT SteveL-MSFT modified the milestones: Post-3.0, 3.1-Consider Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement The issue is a feature or idea
Projects
None yet
Development

No branches or pull requests

3 participants