Skip to content

[usage] Setup usage reset job #14189

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 1 commit into from
Oct 26, 2022
Merged

[usage] Setup usage reset job #14189

merged 1 commit into from
Oct 26, 2022

Conversation

easyCZ
Copy link
Member

@easyCZ easyCZ commented Oct 26, 2022

Description

Initial setup for usage reset job. Currently does nothing but logs when it's triggered.
Config in the installer will be added in subsequent PR.

Related Issue(s)

How to test

Release Notes

NONE

Documentation

Werft options:

  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-integration-tests=all
    Valid options are all, workspace, webapp, ide

@easyCZ easyCZ requested a review from a team October 26, 2022 12:14
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Oct 26, 2022
@easyCZ easyCZ force-pushed the mp/usage-reset-usage-job-setup branch from d55accc to a296d51 Compare October 26, 2022 12:21
@easyCZ easyCZ force-pushed the mp/usage-reset-usage-job-setup branch from a296d51 to 54bc3e0 Compare October 26, 2022 12:36
@easyCZ easyCZ force-pushed the mp/usage-reset-usage-job-setup branch from e3f3dbc to 8138015 Compare October 26, 2022 12:41
@roboquat roboquat merged commit 7532f3c into main Oct 26, 2022
@roboquat roboquat deleted the mp/usage-reset-usage-job-setup branch October 26, 2022 12:46
@svenefftinge
Copy link
Member

I would have preferred to call this in the existing ledger job after the sync. I think it's simpler and would also help with making sure the usage for the time we use was reconciled.

@easyCZ
Copy link
Member Author

easyCZ commented Oct 27, 2022

@svenefftinge My thinking here is that the usage reset should be lighter weight in terms of compute time and should run more frequently. I wanted to avoid coupling them if we need to adjust the frequency on either without being limited to the runtime of the usage reconcile.

But you make a good point. They could run in the same control loop. In either case, we shouldn't assume that the reset runs shortly after usage reconcile as that may not hold true.

@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Oct 28, 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/M team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants