Lower hosted agent session idle timeout minimum to 120 seconds - #9728
Conversation
Relax the client-side validation floor for sessionConfiguration.idleTimeoutSeconds from 300 to 120 seconds (2 minutes) ahead of the upcoming server-side change. The maximum remains 3600 seconds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Thank you for your contribution Deeksha Sharma (@Deeksharma)! We will review the pull request and get back to you soon. |
|
Azure Pipelines: Successfully started running 1 pipeline(s). 18 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
Lowers hosted-agent session idle timeout validation from 300 to 120 seconds across implementation, schemas, and documentation.
Changes:
- Updates the minimum timeout constant and API documentation.
- Synchronizes both JSON schemas and README guidance.
- Adjusts schema boundary tests for 120/119 seconds.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
schemas/azure.ai.agent.json |
Lowers the schema minimum to 120. |
schemas/Agent.json |
Synchronizes the alternate schema constraint. |
README.md |
Documents the new valid range. |
internal/project/doc_examples_test.go |
Updates minimum-boundary schema tests. |
internal/pkg/agents/agent_yaml/yaml.go |
Changes the validation minimum constant. |
internal/pkg/agents/agent_api/models.go |
Updates API model documentation. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Hi @Deeksha Sharma (@Deeksharma). Thank you for your interest in helping to improve the Azure Developer CLI experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Summary
Relaxes the client-side validation floor for
sessionConfiguration.idleTimeoutSecondson hosted agents from 300 to 120 seconds (2 minutes), ahead of the corresponding upcoming server-side change. The maximum remains 3600 seconds.This follows up on #9612, which introduced
sessionConfiguration.idleTimeoutSecondssupport in theazure.ai.agentsextension.Changes
agent_yaml/yaml.go—MinSessionIdleTimeoutSeconds300 → 120; updated doc comment.agent_api/models.go— updated range in doc comment to 120–3600.schemas/azure.ai.agent.json&schemas/Agent.json—minimum300 → 120; updated descriptions.README.md— "between 120 and 3600 seconds".doc_examples_test.go— min-valid boundary → 120, below-min → 119.Behavior
session_configurationis left out of the request and the service applies its default (900 seconds).Tests
Min/MaxSessionIdleTimeoutSecondsconstants and adapt automatically.gofmtclean,go build ./...passes, and fullagent_yaml+projectpackage tests pass.