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

azure app service: lack of required field in api #22714

Open
xiaxyi opened this issue Feb 21, 2023 · 2 comments
Open

azure app service: lack of required field in api #22714

xiaxyi opened this issue Feb 21, 2023 · 2 comments
Labels
App Services Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@xiaxyi
Copy link

xiaxyi commented Feb 21, 2023

When updating azure function/ web app's PublishingCredentialsPolicies, location is required in request body using put . However, it doesn't present in the api.

image

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

ghost commented Feb 21, 2023

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

Issue Details

When updating azure function/ web app's PublishingCredentialsPolicies, location is required in request body using put . However, it doesn't present in the api.

image

Author: xiaxyi
Assignees: -
Labels:

App Services, Service Attention, needs-triage

Milestone: -

@guidojw
Copy link

guidojw commented Jun 15, 2023

@JackTn @antcp @AzureAppServiceCLI when will this follow-up take place?

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

No branches or pull requests

3 participants