You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to delete services created by CloudDebug integration tests when deinstrument fails (#2411)
- On deinstrument failure, the ecs services were not cleaned up properly. This has lead to multiple zombie services in our integration test accounts
- Also simplify the code using waiters
Copy file name to clipboardExpand all lines: jetbrains-core/src/software/aws/toolkits/jetbrains/services/clouddebug/actions/DeinstrumentResourceAction.kt
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,7 @@ class DeinstrumentResourceFromExplorerAction : SingleResourceNodeAction<EcsServi
44
44
project:Project,
45
45
clusterArn:String,
46
46
instrumentedResourceName:String,
47
-
selected:EcsServiceNode?,
48
-
callback: ((Boolean) ->Unit)? = null
47
+
selected:EcsServiceNode?
49
48
) {
50
49
val originalServiceName =EcsUtils.originalServiceName(instrumentedResourceName)
51
50
DeinstrumentAction(
@@ -55,7 +54,7 @@ class DeinstrumentResourceFromExplorerAction : SingleResourceNodeAction<EcsServi
Copy file name to clipboardExpand all lines: jetbrains-core/src/software/aws/toolkits/jetbrains/services/clouddebug/actions/InstrumentResourceAction.kt
0 commit comments