Record resource details in each usage payload #607
Merged
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
grzegorz-roboflow
requested review from
PawelPeczek-Roboflow,
yeldarby,
probicheaux and
hansent
as code owners
PawelPeczek-Roboflow
approved these changes
Aug 26, 2024
grzegorz-roboflow
deleted the
include-resource-details-in-each-usage-payload
branch
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.
Description
Usage payload was recorded only in first payload. This PR is changing this behavior, resource details are recorded in each usage payload
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
CI tests are passing; inspected payloads and confirmed resource details are in each usage payload
Any specific deployment considerations
N/A
Docs
N/A