a365 publish command fails when manifest directory exists already

[pdwarf]

Description

when the /manifest directory already exists, e.g. because the publish command failed half way, the CLI will not include the agenticUserManifestTemplate.json in the zip, and throw an error like

ERROR: Package upload failed (BadRequest). Body:
{"Error":{"Code":"BadRequest","Message":"Manifest schema is not valid. Errors: Error parsing agentic user template: File not found in the zip archive."}}

To work around that, you have to remove the manifest directory altogether, then run a365 publish again, and it works.

Expected behavior

Would be nice if the agenticUserManifestTemplate.json got consistently included in the manifest.zip to make for a smooth process of pushing the blueprint to MAC.

SDK Version

1.1.94-preview+61107da00a

Language/Runtime

.NET 8

OS

macOS 15.7.3 (24G419)

How to Reproduce

Go through all the cli steps until a365 publish, but introduce an issue that'll make this step fail, e.g. the URLs have a regex validation that fails if they don't start with https://...

See how in the initial terminal output, the manifest.zip will include the agenticUserTemplate.... but when you run a365 publish again after fixing the issue with the URL, the above error will occur

Output

No response

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 issue describes unexpected behavior where the CLI fails to include a required file in the manifest.zip under specific conditions.
Priority: Assigned P2 because the issue disrupts the publishing process, but there is a documented workaround of removing the manifest directory and retrying the command.
Copilot: The issue involves debugging and modifying CLI behavior, which requires understanding the workflow and error handling logic. This is beyond Copilot's capability to fix autonomously as it may require changes across multiple files and a deeper understanding of the business logic.
Assignment: Grant Harris has expertise in backend development, CLI tools, and .NET, which aligns closely with the issue's context involving the CLI and .NET runtime. Additionally, he has fewer contributions compared to the tech lead, making him a balanced choice for workload distribution.
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 issue describes unexpected behavior where the CLI fails to include a required file in the manifest.zip under specific conditions.

priority rationale: Assigned P2 because the issue disrupts the publishing process, but there is a documented workaround of removing the manifest directory and retrying the command.

copilot rationale: The issue involves debugging and modifying CLI behavior, which requires understanding the workflow and error handling logic. This is beyond Copilot's capability to fix autonomously as it may require changes across multiple files and a deeper understanding of the business logic.

assignment rationale: Grant Harris has expertise in backend development, CLI tools, and .NET, which aligns closely with the issue's context involving the CLI and .NET runtime. Additionally, he has fewer contributions compared to the tech lead, making him a balanced choice for workload distribution.

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

[SUGGESTION] Suggested Approach

1. Inspect the logic in the a365 publish command implementation, likely located in src/Commands/PublishCommand.cs or similar. Specifically, check how the manifest directory and agenticUserManifestTemplate.json are handled during the zip creation process and ensure the file is consistently included.
2. Add a pre-check in the a365 publish command to detect if the /manifest directory already exists. If it does, either clean up the directory or ensure all required files, including agenticUserManifestTemplate.json, are present before proceeding with the zip creation.
3. Update the error handling mechanism in the a365 publish command to provide clearer guidance when the agenticUserManifestTemplate.json is missing. Suggest users to clean up the /manifest directory or automatically retry the process after fixing the issue.
4. Write a unit test in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Integration to simulate the scenario where the /manifest directory exists but is incomplete. Validate that the a365 publish command correctly includes all required files in the zip and handles retries gracefully.
5. Document the behavior and workaround in the docs directory, specifically in the CLI usage guide. Include a troubleshooting section that explains how to handle errors related to the /manifest directory and missing files during the a365 publish command execution.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models

[github-actions]

SLA Escalation Alert

This P2 issue has exceeded its SLA threshold.

Metric	Value
Priority	P2
SLA Threshold	72 hours
Time Since Update	82.4 hours
Current Assignees	@gwharris7

Action: Adding Tech Lead @sellakumaran as assignee for immediate attention.

cc: @ajmfehr

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P2 issue has exceeded its SLA threshold.

Metric	Value
Priority	P2
SLA Threshold	72 hours
Time Since Update	95.8 hours
Current Assignees	@gwharris7, @sellakumaran, @Copilot

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P2 issue has exceeded its SLA threshold.

Metric	Value
Priority	P2
SLA Threshold	72 hours
Time Since Update	72.1 hours
Current Assignees	@gwharris7, @sellakumaran, @Copilot

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation