-
Notifications
You must be signed in to change notification settings - Fork 734
feat(cwl): Add clear screen and stop session code lens #5958
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
Changes from 2 commits
4a7a75f
1f8d9dd
104fb2c
432ecf1
9b2c3a7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -13,7 +13,7 @@ import { | |||||||||
| LiveTailSessionUpdate, | ||||||||||
| StartLiveTailResponseStream, | ||||||||||
| } from '@aws-sdk/client-cloudwatch-logs' | ||||||||||
| import { globals, ToolkitError } from '../../../shared' | ||||||||||
| import { getLogger, ToolkitError } from '../../../shared' | ||||||||||
|
|
||||||||||
| export async function tailLogGroup( | ||||||||||
| registry: LiveTailSessionRegistry, | ||||||||||
|
|
@@ -32,32 +32,29 @@ export async function tailLogGroup( | |||||||||
| region: wizardResponse.regionLogGroupSubmenuResponse.region, | ||||||||||
| } | ||||||||||
| const session = new LiveTailSession(liveTailSessionConfig) | ||||||||||
| if (registry.has(session.uri)) { | ||||||||||
| if (registry.has(session.uri.toString())) { | ||||||||||
|
||||||||||
| export function uriToKey(uri: vscode.Uri): string { |
toString is not reliable, querystring parameters can appear in arbitrary order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aws-toolkit-vscode/packages/core/src/awsService/cloudWatchLogs/registry/logDataRegistry.ts
Lines 51 to 53 in d4d1ae0
| public isRegistered(uri: vscode.Uri): boolean { | |
| return this.registry.has(uriToKey(uri)) | |
| } |
This makes me wonder why LiveTailSessionRegistry is using a completely different pattern than LogDataRegistry. Now we have two different "registries" concepts to maintain, using completely different patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the aim of these two registries are different from one another.
Given a LiveTail session has its own components unique to other CWL experiences (own client, abortController, responseStream, etc.) We have a LiveTailSession object, that has a long running lifeCycle. This lifecycle can end from outside the TailLogGroup command, and so this registry is really just there to track what Sessions are currently running, so when a session needs to be closed via a CodeLens, or closing its textEditors, we can find the LiveTailSession from its uri and abort the response stream and clean up its resources.
I think this is a separate responsiblity from the LogDataRegistry that is actually persisting LogData, and making requests to FilterLogEvents.
keeganirby marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
keeganirby marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| /*! | ||
| * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. | ||
| * SPDX-License-Identifier: Apache-2.0 | ||
| */ | ||
|
|
||
| import * as vscode from 'vscode' | ||
| import { cloudwatchLogsLiveTailScheme } from '../../../shared/constants' | ||
|
|
||
| export class LiveTailCodeLensProvider implements vscode.CodeLensProvider { | ||
| onDidChangeCodeLenses?: vscode.Event<void> | undefined | ||
|
|
||
| provideCodeLenses( | ||
| document: vscode.TextDocument, | ||
| token: vscode.CancellationToken | ||
| ): vscode.ProviderResult<vscode.CodeLens[]> { | ||
| const uri = document.uri | ||
| if (uri.scheme !== cloudwatchLogsLiveTailScheme) { | ||
| return [] | ||
| } | ||
| const codeLenses: vscode.CodeLens[] = [] | ||
| codeLenses.push(this.buildClearDocumentCodeLens(document)) | ||
| codeLenses.push(this.buildStopTailingCodeLens(document)) | ||
| return codeLenses | ||
| } | ||
|
|
||
| private buildClearDocumentCodeLens(document: vscode.TextDocument): vscode.CodeLens { | ||
| const range = this.getBottomOfDocumentRange(document) | ||
| const command: vscode.Command = { | ||
| title: 'Clear document', | ||
| command: 'aws.cwl.clearDocument', | ||
| arguments: [document], | ||
| } | ||
| return new vscode.CodeLens(range, command) | ||
| } | ||
|
|
||
| private buildStopTailingCodeLens(document: vscode.TextDocument): vscode.CodeLens { | ||
| const range = this.getBottomOfDocumentRange(document) | ||
| const command: vscode.Command = { | ||
| title: 'Stop tailing', | ||
| command: 'aws.cwl.stopTailingLogGroup', | ||
| arguments: [document], | ||
| } | ||
| return new vscode.CodeLens(range, command) | ||
| } | ||
|
|
||
| private getBottomOfDocumentRange(document: vscode.TextDocument): vscode.Range { | ||
| return new vscode.Range( | ||
| new vscode.Position(document.lineCount - 1, 0), | ||
| new vscode.Position(document.lineCount - 1, 0) | ||
| ) | ||
| } | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have a different scheme, and a different codelens, for "live tail"? The codelenses for the non-livetail log group search would be useful in live tail. Why are they separate?
Whether a log group is being "tailed" or not is just a flag. It's not an entirely different concept.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CodeLenses in the existing CWL experiences are not very applicable to our LiveTail use case.
"Load newer" & "Load older" don't apply when data is being streamed in constantly. For
View full log stream, customers can apply LogStream filter parameters to their liveTail session already so having this as a codeLens in a Livetail session doesn't seem necessary.On the other hand, a
SearchLogGroupcommand won't need aStop tailingcode lens.These UX are quite separate.
We already separate the CodeLens providers for
logDataandlogStream. Given the UX and functionality of LiveTail is different from our other experiences I think it fits to have a separate CodeLens provider.This is the same reasoning behind having a separate scheme as we discussed here. The way we retrieve/display logs from a LiveTail session stream differs enough from the existing LogDataRegistry that I felt that it was best to separate these logic's, as opposed to finding a way to generalize.
I feel that LiveTail and the existing experiences are separate enough from each other that they should be treated as such.