-
Notifications
You must be signed in to change notification settings - Fork 61
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
fix(Usage Reports): re-gen service after recent API changes #320
Conversation
Signed-off-by: Jonathan Date-Chong <[email protected]>
@Jdatechong it looks like you used a fairly old version of the SDK generator (3.75.0) to regen this service. Please install the latest version of the generator (currently 3.89.0) and regen with that. |
@Jdatechong just wanted to double-check that you saw my comment above about needing to re-gen the go and java sdk code with a recent version of the SDK generator. I've merged the node and python PRs so as of right now, your service is not in sync between go/java vs node/python. |
Signed-off-by: Jonathan Date-Chong <[email protected]>
Signed-off-by: Jonathan Date-Chong <[email protected]>
@padamstx the go and java sdks have been regenerated with a newer version of the sdk generator test results after update:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
## [0.62.6](v0.62.5...v0.62.6) (2024-04-18) ### Bug Fixes * **Usage Reports:** re-gen service after recent API changes ([#320](#320)) ([aad1c24](aad1c24))
🎉 This PR is included in version 0.62.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR summary
Regeneration of the usage reports service. Mainly intended to add
catalog_id
toinstance_usage
andresource
.PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Does this PR introduce a breaking change?
Other information
Test results:
Integration tests:
Examples: