Enable create-instance command

[sellakumaran]

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'feature' because the issue requests enabling a command, which suggests adding new functionality.
Priority: Assigned P2 because it is an enhancement that adds functionality and aligns with the 'feature' keyword in the priority reference.
Copilot: The issue lacks a description and clear requirements, making it too vague for Copilot to address. Without specific details about what 'enable create-instance command' entails, Copilot cannot determine the scope or implementation path.
Assignment: Josh Oratz is a backend engineer with expertise in CLI development, which aligns well with the 'create-instance' command feature. Additionally, his contribution count (18) is lower than Mrunal Hirve's (25), making him a better choice for workload balance.
Labels: Applied labels enhancement, P2 based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: feature
Priority: P2
Confidence: 95.0%

Recommended Assignee: @joratz

Analysis:
type rationale: Classified as 'feature' because the issue requests enabling a command, which suggests adding new functionality.

priority rationale: Assigned P2 because it is an enhancement that adds functionality and aligns with the 'feature' keyword in the priority reference.

copilot rationale: The issue lacks a description and clear requirements, making it too vague for Copilot to address. Without specific details about what 'enable create-instance command' entails, Copilot cannot determine the scope or implementation path.

assignment rationale: Josh Oratz is a backend engineer with expertise in CLI development, which aligns well with the 'create-instance' command feature. Additionally, his contribution count (18) is lower than Mrunal Hirve's (25), making him a better choice for workload balance.

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

[SUGGESTION] Suggested Approach

1. Implement the create-instance command in the CLI by adding a new command handler in the src/Microsoft.Agents.A365.DevTools.Cli/Commands directory. Follow the existing patterns used for other commands, such as deploy-instance or update-instance, to ensure consistency.
2. Define the logic for instance creation in a dedicated service class under src/Microsoft.Agents.A365.DevTools.Cli/Services. Use Azure Functions or Azure DevOps APIs (referenced in autoTriage/requirements.txt) for provisioning resources, and ensure proper error handling and logging.
3. Update the command parser in src/Microsoft.Agents.A365.DevTools.Cli/Program.cs to register the new create-instance command. Include necessary arguments, such as instance name, region, and configuration options, to make the command flexible and user-friendly.
4. Write unit tests for the create-instance command in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/MockToolingServer and src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/TestSupport. Mock dependencies like Azure APIs using libraries such as pytest-mock or equivalent C# mocking frameworks to ensure robust testing.
5. Update the documentation in the docs directory to include usage instructions for the create-instance command. Provide examples of command syntax and expected outputs, and ensure the README file reflects the new functionality.

---

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	84.8 hours
Current Assignees	@sellakumaran

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.2 hours
Current Assignees	@sellakumaran

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	95.8 hours
Current Assignees	@sellakumaran

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