Skip to content

Agent invocation fixes#2842

Merged
vigoo merged 20 commits intomainfrom
agent-invocation-fixes
Feb 26, 2026
Merged

Agent invocation fixes#2842
vigoo merged 20 commits intomainfrom
agent-invocation-fixes

Conversation

@vigoo
Copy link
Contributor

@vigoo vigoo commented Feb 26, 2026

Attemps to fix all the issues that came by merging #2819 with broken checks (that were reported as green).

In details:

Agent Invocation API Fixes

  • Fixes idempotency key handling on the new agent invocation API
  • Deployment revision support added to the invocation API, this supports invoking older agents (with different agent types)
  • Agent metadata casing inconsistency fixes (kebab vs non-kebab in various places)

Registry / Deployment

  • Required some changes to support the version of the invocation API when it has a specific deployment revision.

Test Infrastructure Improvements

  • The integration test framework now captures and re-emits the child process logs properly with all information (log level, nested spans, attributes) so I can finally read the integration test output!
  • Fail on missing test reports in CI (this would have prevented the merge yesterday)
  • Fix in cargo-test-r to fail if the child cargo-test was aborted

Other

  • Some changes to AGENTS.md / extracting things to SKILLs
  • Deleted unused component-transformer-example1

@github-actions
Copy link

github-actions bot commented Feb 26, 2026

✅ All contributors have signed the CLA.
Posted by the CLA Assistant Lite bot.

})?;
self.registry_service
.resolve_agent_type_at_deployment(
&auth.account_id(),
Copy link
Contributor

@mschuwalow mschuwalow Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This suffers from the same problem of only behaving correctly on the user's own account

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that's a separate ticket, not trying to solve in this one (#2836)

RegisteredAgentType agent_type = 1;
}

message ResolveAgentTypeAtDeploymentRequest {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the plan is to allow cross-account resolution of accounts / this is ever called with a user provided account id, we need to pass the auth context here. Otherwise, the currently used system auth context is going to bypass permission checks and potentially allow users to access data they should not be able to access.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This mirrors the existing ResolveLatestAgentTypeByNamesRequest just has a deployment_revision field

// deploy environment to make component visible
self.deploy_environment(&component.environment_id).await?;
let deployment = self.deploy_environment(&component.environment_id).await?;
self.last_deployments
Copy link
Contributor

@mschuwalow mschuwalow Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The auto_deployment stuff is only to allow the worker-executor style tests (which assume a component is ready as soon as its created) to work with the test dsl.

For integration tests if think an explicit user.deploy_environment(&environmentId) is clearer and gives you the deployment revision that you need.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like being able to copy a worker executor test to an integration test so I don't think this feature hurts

@vigoo
Copy link
Contributor Author

vigoo commented Feb 26, 2026

I have read the CLA Document and I hereby sign the CLA

github-actions bot added a commit that referenced this pull request Feb 26, 2026
@vigoo vigoo merged commit 26e6daa into main Feb 26, 2026
70 of 72 checks passed
@vigoo vigoo deleted the agent-invocation-fixes branch February 26, 2026 16:22
@github-actions github-actions bot locked and limited conversation to collaborators Feb 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants