-
Notifications
You must be signed in to change notification settings - Fork 877
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
Add eTag field for consumption API #15303
Comments
Hi @stephybun thanks for this issue! Our SDK is generated based on swagger. I checked swagger after 2019-10-01 and there is no eTag attribute in BudgetProperties. Sorry for that. |
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
Thanks for the response @804873052, could you then please add the field to the swagger spec so that it can be generated in the SDK? |
@stephybun Swagger is maintained by the service team and I cannot modify it directly. I found that Budget has a root level ETag field, you see https://github.com/Azure/azure-sdk-for-go/blob/main/services/consumption/mgmt/2019-10-01/consumption/models.go#L232 |
@804873052 thanks for pointing the field out on root level, must have missed it. Unfortunately the reason we thought we needed the ETag was for toggling the |
Close this one as this is related to Swagger/service behaviour. |
Feature Request
Hello, we're using this sdk to perform CRUD operations on budgets on subscription and resource group level. In order to update certain fields in a budget the eTag of the budget needs to be sent in the update request. Unfortunately the current consumption API version from 2019-10-01 does not have support for the eTag yet - as an example see BudgetProperties below.
Can you please add support for the eTag field?
The text was updated successfully, but these errors were encountered: