the Blueprint is still visible in MAC->Agent after running "a365 cleanup"

[frankchen76]

Description

I was trying to delete a blueprint via run "a365 cleanup". All Entra Id resources were gone. however, the blueprint is still visible in MAC->Agent inventory page.

Expected behavior

the Blueprint should be removed from MAC as well

SDK Version

"@microsoft/agents-a365-runtime": "^0.1.0-preview.30", CLI: 1.1.104-preview+80f983b74

Language/Runtime

node.js v22.18.0

OS

Windows 11

How to Reproduce

1. Run "a365 cleanup"
2. check the Blueprint from MAC->Agent

Output

the below output indicated the blueprint was removed, but the blueprint is still visible in MAC-> Agent

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'bug' because the user reports unexpected behavior where the blueprint is not fully removed despite running the cleanup command.
Priority: Assigned P2 because it affects user experience and could lead to confusion, but does not appear to block critical functionality or have widespread impact.
Copilot: This issue involves debugging a bug related to the visibility of a blueprint in the MAC->Agent inventory after running a cleanup command. It likely requires understanding the interaction between the CLI command, SDK, and inventory page, which is beyond Copilot's capabilities for autonomous fixes.
Assignment: Grant Harris has expertise in backend development and CLI tools, which are relevant to the issue involving the 'a365 cleanup' command and backend behavior. Additionally, he has a lower contribution count compared to the tech lead, making him a suitable choice for workload balance.
Labels: Applied labels bug, P2 based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: bug
Priority: P2
Confidence: 95.0%

Recommended Assignee: @gwharris7

Analysis:
type rationale: Classified as 'bug' because the user reports unexpected behavior where the blueprint is not fully removed despite running the cleanup command.

priority rationale: Assigned P2 because it affects user experience and could lead to confusion, but does not appear to block critical functionality or have widespread impact.

copilot rationale: This issue involves debugging a bug related to the visibility of a blueprint in the MAC->Agent inventory after running a cleanup command. It likely requires understanding the interaction between the CLI command, SDK, and inventory page, which is beyond Copilot's capabilities for autonomous fixes.

assignment rationale: Grant Harris has expertise in backend development and CLI tools, which are relevant to the issue involving the 'a365 cleanup' command and backend behavior. Additionally, he has a lower contribution count compared to the tech lead, making him a suitable choice for workload balance.

labels rationale: Applied labels bug, P2 based on issue type and priority

[SUGGESTION] Suggested Approach

1. Investigate the cleanup logic in the CLI command implementation for a365 cleanup located in the src/Commands directory. Specifically, check if the command properly triggers the removal of blueprints from the MAC->Agent inventory. Look for any missing API calls or incomplete cleanup steps.
2. Verify the integration with the MAC->Agent inventory API. Check if the blueprint deletion process includes a call to the relevant API endpoint to update the inventory. This might involve reviewing the HTTP request logic in the src/Services or src/Utils directories, or any related API client implementation.
3. Add logging or debugging statements in the a365 cleanup command to confirm whether the blueprint deletion process includes the MAC->Agent inventory update. This will help identify if the issue lies in the CLI logic or the backend API response.
4. Review the test cases in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Commands to ensure there is adequate coverage for the a365 cleanup command, particularly for scenarios involving blueprint cleanup and inventory updates. If missing, add tests to simulate this behavior and validate the expected outcome.
5. Check for potential caching issues in the MAC->Agent inventory page. If the blueprint is removed successfully but still visible, it could be due to a delay in cache invalidation. Investigate whether the MAC->Agent UI fetches updated data after the cleanup operation and ensure proper cache refresh mechanisms are in place.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models