Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: accept payload on workspace usage route#13544

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
f0ssel merged 12 commits intomainfromf0ssel/usage-payload
Jun 14, 2024
Merged

Conversation

f0ssel
Copy link
Contributor

@f0sself0ssel commentedJun 11, 2024
edited
Loading

This adds new behavior to the workspace usage endpoint to accept a payload containing anAgentID andAppName. This is so the CLI can start informing us of activity based on different "defined apps". This is currently behind an experiment flagworkspace-usage which it will stay behind until we are reading to migrate fromworkspace_agent_stats table toworkspace_app_stats.

@f0sself0ssel marked this pull request as ready for reviewJune 12, 2024 18:30
@f0sself0ssel requested a review fromjohnstcnJune 12, 2024 18:37
@@ -137,7 +137,7 @@ func (r *RootCmd) portForward() *serpent.Command {
listeners[i] = l
}

stopUpdating := client.UpdateWorkspaceUsageContext(ctx, workspace.ID)
stopUpdating := client.UpdateWorkspaceUsageContext(ctx, workspace.ID, codersdk.PostWorkspaceUsageRequest{})
Copy link
Member

Choose a reason for hiding this comment

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

non-blocking: We might want to expose this as an app named "port-forward" or similar?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I believe this will require we add a field to theworkspace_agent_stats table which is a change I did not want to include in this PR. In general, do you think it's a good idea to add this field given it may impact other features like insights?

Copy link
Member

Choose a reason for hiding this comment

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

Let's leave it for now. I'd like to avoid any insights changes in the course of this refactor.

f0ssel reacted with thumbs up emoji
@f0sself0ssel requested a review fromjohnstcnJune 13, 2024 20:57
@f0sself0ssel merged commit44d6913 intomainJun 14, 2024
31 checks passed
@f0sself0ssel deleted the f0ssel/usage-payload branchJune 14, 2024 14:08
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJun 14, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@johnstcnjohnstcnjohnstcn approved these changes

Assignees

@f0sself0ssel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@f0ssel@johnstcn

[8]ページ先頭

©2009-2025 Movatter.jp