Skip to content

docs(aws-transform-agent-toolkit): pass required owner_contact_info to deploy pipeline#156

Merged
nadetastic merged 2 commits into
kirodotdev:mainfrom
anychen1:anychen/atx-toolkit-owner-contact-info
Jun 26, 2026
Merged

docs(aws-transform-agent-toolkit): pass required owner_contact_info to deploy pipeline#156
nadetastic merged 2 commits into
kirodotdev:mainfrom
anychen1:anychen/atx-toolkit-owner-contact-info

Conversation

@anychen1

Copy link
Copy Markdown
Contributor

What

Companion to awslabs/agent-builder-toolkit-aws-transform#67, which makes
owner_contact_info a required argument of deploy_agent_full_pipeline.

That argument populates the agent's ownerContactInfo and the Agent Provider
extension contactInfo, which the AWS Transform registry's agent-card
validation rejects when empty. With the tool arg now required, the steering must
collect and pass it, otherwise the guided deploy flow calls the tool without the
required argument.

Change

  • deploy-agent-workflow.md:
    • Add an "Owner contact" question to the Step 1 information gathering and
      renumber the subsequent questions.
    • Add owner_contact_info to the Step 2 call example and the key-parameters
      list.
    • Update the Force CodeBuild and Custom IAM Roles examples to pass it.
    • Note in the skip_registry example that a contact is not required in that mode.
  • deployment-pipeline-guide.md:
    • Add owner_contact_info to the MCP deployment-tools example.

Docs only.

…o deploy pipeline

deploy_agent_full_pipeline now requires owner_contact_info — it populates the
agent's ownerContactInfo and the Agent Provider contactInfo, which the registry
rejects when empty. Update the deploy workflow and pipeline guide so the guided
flow collects an owner contact (new gather-step question) and every tool example
passes it. The skip_registry example notes a contact is not required in that mode.
Comment thread aws-transform-agent-toolkit/steering/deploy-agent-workflow.md Outdated
@nadetastic nadetastic merged commit 0821ead into kirodotdev:main Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants