Skip to content

fix(container-group): trigger new status update after full removal #61

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
Oct 24, 2024

Conversation

reubenmiller
Copy link
Collaborator

Only call the new container status update after finishing the compose down calls

Copy link

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
7 0 1 7 100 1m21.755s

Passed Tests

Name ⏱️ Duration Suite
Get Configuration 5.243 s Operations
Install container-group package 16.410 s Operations
Install container-group with multiple files 28.551 s Operations
Uninstall container-group 2.868 s Operations
Install container package 16.087 s Operations
Uninstall container package 4.868 s Operations
Service status 7.727 s Telemetry-Main

Merged via the queue into main with commit 9b4a90f Oct 24, 2024
3 checks passed
@reubenmiller reubenmiller deleted the fix-container-group-removal-trigger branch November 7, 2024 21:06
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.

1 participant