-
Notifications
You must be signed in to change notification settings - Fork 5.6k
BillingRP - Adding new fields to transactions API #8232
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding new fields to transactions API
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
This was referenced Jan 25, 2020
allenjzhang
reviewed
Jan 25, 2020
...ification/billing/resource-manager/Microsoft.Billing/preview/2019-10-01-preview/billing.json
Outdated
Show resolved
Hide resolved
|
Azure Pipelines successfully started running 1 pipeline(s). |
3 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Updated the field description
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@allenjzhang I have incorporated the review comments. Please take a look. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@allenjzhang Please review and merge the PR. |
allenjzhang
approved these changes
Jan 29, 2020
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@allenjzhang Please merge the PR. |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
ssripadham
pushed a commit
to ssripadham/azure-rest-api-specs
that referenced
this pull request
Feb 21, 2020
* Adding new fields to transactions API Adding new fields to transactions API * Updated the field description Updated the field description * Updated few descriptions
00Kai0
pushed a commit
to 00Kai0/azure-rest-api-specs
that referenced
this pull request
Oct 12, 2020
* Adding new fields to transactions API Adding new fields to transactions API * Updated the field description Updated the field description * Updated few descriptions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ARMSignedOff
<valid label in PR review process>add this label when ARM approve updates after review
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding new fields to transactions API
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.