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

automation: source and logProgress of dscConfiguration not respond by GET API #24728

Open
wuxu92 opened this issue Jul 7, 2023 · 1 comment
Labels
Automation Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@wuxu92
Copy link

wuxu92 commented Jul 7, 2023

related swagger link:

"logProgress": {
"type": "boolean",
"description": "Gets or sets progress log option."
},
"source": {
"$ref": "#/definitions/ContentSource",
"description": "Gets or sets the source."
},

we can set in PUT request, but the GET didnot return these properties. the logProgess field even not defined in the GET Reseponse.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 7, 2023
@JackTn JackTn added Automation Service Attention Workflow: This issue is responsible by Azure service team. labels Jul 11, 2023
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 11, 2023
@ghost
Copy link

ghost commented Jul 11, 2023

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jaspkaur28.

Issue Details

related swagger link:

"logProgress": {
"type": "boolean",
"description": "Gets or sets progress log option."
},
"source": {
"$ref": "#/definitions/ContentSource",
"description": "Gets or sets the source."
},

we can set in PUT request, but the GET didnot return these properties. the logProgess field even not defined in the GET Reseponse.

Author: wuxu92
Assignees: -
Labels:

Automation, Service Attention, needs-triage

Milestone: -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Automation Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants