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

[BUG] Reservation Transactions - List By Billing Profile API required EventDate in $filter #29544

Open
thangdoominh opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue points to a problem in the management-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@thangdoominh
Copy link

API Spec link

https://learn.microsoft.com/en-us/rest/api/consumption/reservation-transactions/list-by-billing-profile?view=rest-consumption-2023-05-01&tabs=HTTP

API Spec version

2023-05-01

Describe the bug

  • REST API required EventDate but the document doesn't require the $filter

Expected behavior

  • Don't require the EventDate in $filter
  • Or Update the document that requires the EventDate in $filter

Actual behavior

  • $filter required EventDate. When I don't pass the $filter the response raises error
  • Response:
  "error": {
    "code": "400",
    "message": "EventDate should have beginning range value. (Request ID: 6eb6cf24-ea0b-4eaa-a426-4e7c161dab7e)"
  }
}

Reproduction Steps

  1. Go https://learn.microsoft.com/en-us/rest/api/consumption/reservation-transactions/list-by-billing-profile?view=rest-consumption-2023-05-01&tabs=HTTP
  2. Sign in with your Azure account
  3. Input the billingAccountId, billingProfileId, api-version: 2023-05-01
  4. Click Run button

Environment

No response

@thangdoominh thangdoominh added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jun 21, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Jun 21, 2024
@v-jiaodi v-jiaodi added the Mgmt This issue points to a problem in the management-plane of the library. label Jul 2, 2024
@v-jiaodi
Copy link
Member

v-jiaodi commented Jul 2, 2024

@bradenwatkins Please help take a look, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue points to a problem in the management-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants