-
Notifications
You must be signed in to change notification settings - Fork 433
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
Flex Deployment Changes #3625
Flex Deployment Changes #3625
Conversation
string functionAppString = JsonConvert.SerializeObject(functionApp); | ||
|
||
url = new Uri($"{managementURL}{site.SiteId}?api-version={ArmUriTemplates.FlexApiVersion}"); | ||
await ArmHttpAsyncForFlex(new HttpMethod("PATCH"), url, accessToken, functionApp); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, we currently can't do a PATCH request to update attributes, we'll need to do a PUT.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kamperiadis! Can you please share the recommended API. I got it from my local AZ CLI copy which was using Patch. Interestingly, it is actually working in beta :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just confirmed with David today - we did not do any implementation changes for PATCH, which might be missing things like blocking unsupported configs in the Site object. I would not suggest using PATCH. Instead, we should be doing a GET call to the function app and then do a PUT request with that same function app object but with the updated values.
Not sure what Az CLI copy you have but for flex specifically, the Az CLI makes PUT calls when updating the runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed it to us PUT
instead of PATCH
.
string functionAppString = JsonConvert.SerializeObject(functionApp); | ||
|
||
url = new Uri($"{managementURL}{site.SiteId}?api-version={ArmUriTemplates.FlexApiVersion}"); | ||
await ArmHttpAsyncForFlex(new HttpMethod("PATCH"), url, accessToken, functionApp); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just confirmed with David today - we did not do any implementation changes for PATCH, which might be missing things like blocking unsupported configs in the Site object. I would not suggest using PATCH. Instead, we should be doing a GET call to the function app and then do a PUT request with that same function app object but with the updated values.
Not sure what Az CLI copy you have but for flex specifically, the Az CLI makes PUT calls when updating the runtime.
Issue describing the changes in this PR
resolves #issue_for_this_pr
Pull request checklist