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

[usage] Proto changes for GetCostCenter RPC #12337

Merged
merged 1 commit into from
Aug 24, 2022

Conversation

laushinka
Copy link
Contributor

Description

Proto changes for the GetCostCenter RPC

Related Issue(s)

Relates #12264

How to test

Release Notes

NONE

Documentation

Werft options:

  • /werft with-preview

@laushinka laushinka requested a review from a team August 24, 2022 09:15
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Aug 24, 2022
Copy link
Member

@easyCZ easyCZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold for Q around precision


message CostCenter {
string attribution_id = 1;
int32 spending_limit = 2;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the precision stored in the DB? Is int32 enough? I'd probably err on the side of caution here and go for int64

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's int(11) which I understand to be 32 bits?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry if we set it to int64 we might truncate something during the conversion?

I will unhold for now to unblock, but we can discuss again what we should store.

@roboquat roboquat merged commit f0e6ee3 into main Aug 24, 2022
@roboquat roboquat deleted the lau/usage-costcenter-proto-12264 branch August 24, 2022 09:38
@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: webapp Meta team change is running in production deployed Change is completely running in production release-note-none size/XXL team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants