Usage Operations #164
Merged
Usage Operations #164
Conversation
This file contains 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
jonfk
approved these changes
Mar 28, 2018
| * @param subscriptionId The value is a GUID formatted subscription-id that identifies the subscription for which usage records are required. | ||
| * @return {@link SubscriptionDailyUsage} | ||
| */ | ||
| ResponseEntity<PartnerCenterResponse<SubscriptionDailyUsage>> getDailySubscriptionUsage(String customerId, String subscriptionId); |
This change includes PartnerUsage, SubscriptionUsageSummary, Subscription(Daily/Monthly)UsageRecord. More to come for SpendingBudget and CustomerUsage
This is mostly to stay in step with Microsoft's own naming.
paulsmelser
force-pushed
the
release/major/new_usage_operations
branch
from
e743141
to
11a76b8
Compare
Spring Social for Microsoft Partner Center
automation
moved this from In progress
to Done
Mar 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #163