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

[RW-13720][risk=no] Cleaned up credit exhaustion cron language #8994

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

evrii
Copy link
Collaborator

@evrii evrii commented Dec 12, 2024

Cleaned up language of credit exhaustion cron as much as practical.

This largely involved changing freetrier to initialcredit and changing expiry to exhaustion.


PR checklist

  • I have included an issue ID or "no ticket" in the PR title as outlined in CONTRIBUTING.md.
  • I have included a risk tag of the form [risk=no|low|moderate|severe] in the PR title as outlined in CONTRIBUTING.md.
  • I have manually tested this change and my testing process is described above.
  • This change includes appropriate automated tests, and I have documented any behavior that cannot be tested with code.
  • I have added explanatory comments where the logic is not obvious.
  • One or more of the following is true:
    • This change is intended to complete a JIRA story, so I have checked that all AC are met for that story.
    • This change fixes a bug, so I have ensured the steps to reproduce are in the Jira ticket or provided above.
    • This change impacts deployment safety (e.g. removing/altering APIs which are in use), so I have documented the impacts in the description.
    • This change includes a new feature flag, so I have created and linked new JIRA tickets to (a) turn on the feature flag and (b) remove it later.
    • This change modifies the UI, so I have taken screenshots or recordings of the new behavior and notified the PO and UX designer in Slack.
    • This change modifies API behavior, so I have run the relevant E2E tests locally because API changes are not covered by our PR checks.
    • None of the above apply to this change.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Duplicating "freecredit" and iinitialcredits" to ensure deploy safety. Plan to delete freetier later.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Change Expiry to Exhaustion to make naming more intuitive.

@evrii evrii changed the title Renamed /cron/checkFreeTierBillingUsage to /cron/checkForInitialCred… [RW-13720][risk=no] Cleaned up credit exhaustion cron language Dec 13, 2024
@evrii evrii marked this pull request as ready for review December 13, 2024 15:52
@@ -1,7 +1,7 @@
cron:
- url: /v1/cron/checkObjectNameSize
schedule: every 24 hours
- url: /v1/cron/checkFreeTierBillingUsage
- url: /v1/cron/checkForInitialCreditUsage
Copy link
Collaborator

Choose a reason for hiding this comment

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

@@ -23,17 +23,25 @@
"projectNamePrefix": "aou-rw-local1-",
"exportBigQueryTable": "all-of-us-workbench-test-bd.billing_data.rw_test_firecloud_view",
"defaultFreeCreditsDollarLimit": 300.0,
"defaultInitialCreditDollarLimit": 300.0,
"freeTierCostAlertThresholds": [
Copy link
Collaborator

Choose a reason for hiding this comment

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

do we need to keep the old ones and user another PR to delete? If our code switches to use the new config, then we can just delete them now. Same for all other configs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants