Skip to content

[dashboard] Use new usage API for team-usage #12677

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
Sep 7, 2022
Merged

[dashboard] Use new usage API for team-usage #12677

merged 1 commit into from
Sep 7, 2022

Conversation

svenefftinge
Copy link
Member

@svenefftinge svenefftinge commented Sep 6, 2022

Description

Connects the team usage view with the new usage API.

Related Issue(s)

Fixes #

How to test

Release Notes

NONE

Documentation

Werft options:

  • /werft with-preview
  • /werft with-payment

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-se-usage-view.9 because the annotations in the pull request description changed
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 6, 2022

/werft run with-preview with-payment

👍 started the job as gitpod-build-se-usage-view.12
(with .werft/ from main)

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-se-usage-view.14 because the annotations in the pull request description changed
(with .werft/ from main)

@svenefftinge svenefftinge reopened this Sep 6, 2022
@roboquat roboquat added size/L and removed size/XS labels Sep 6, 2022
@svenefftinge svenefftinge force-pushed the se/usage-view branch 3 times, most recently from 23fd0d2 to 043b644 Compare September 6, 2022 12:34
@roboquat roboquat added size/XL and removed size/L labels Sep 6, 2022
@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 6, 2022

/werft run

👍 started the job as gitpod-build-se-usage-view.19
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 6, 2022

/werft run clean-slate-deployment=true

👍 started the job as gitpod-build-se-usage-view.20
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 6, 2022

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-se-usage-view.21
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 6, 2022

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-se-usage-view.22
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 7, 2022

/werft run

👍 started the job as gitpod-build-se-usage-view.23
(with .werft/ from main)

@svenefftinge svenefftinge force-pushed the se/usage-view branch 3 times, most recently from 8fc1e2f to eaadb2b Compare September 7, 2022 08:45
@roboquat roboquat added size/XS and removed size/XL labels Sep 7, 2022
@svenefftinge svenefftinge reopened this Sep 7, 2022
@svenefftinge svenefftinge marked this pull request as ready for review September 7, 2022 08:51
@svenefftinge svenefftinge requested a review from a team September 7, 2022 08:51
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Sep 7, 2022
@svenefftinge
Copy link
Member Author

/hold

@svenefftinge
Copy link
Member Author

svenefftinge commented Sep 7, 2022

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-se-usage-view.34
(with .werft/ from main)

@svenefftinge
Copy link
Member Author

/unhold

@roboquat roboquat merged commit 249a563 into main Sep 7, 2022
@roboquat roboquat deleted the se/usage-view branch September 7, 2022 17:00
@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Sep 8, 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/XL team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants