Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Make omitted Gateway protocolType mean unrestricted

已关闭
  • 哪里不对？
#2,084 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws, typescript
领域
cli, infrastructure, release

调研方向

首先追踪旧的 CLI 编写和导入路径、基于项目的重构和 schema 副本，以及 AgentCore L3 Gateway 的合成与测试。在更改行为之前，先审查迁移和依赖版本固定要求。完成的标准是所有列出的验收标准都通过，包括能够证明现有 MCP 项目仍受到限制的回归覆盖。

由索引模型根据 Issue 内容生成。

描述

enhancement
Description

Make an omitted Gateway protocolType consistently mean an unrestricted
Gateway across the old CLI, project schema, and L3 construct.

The current project contract has an unintuitive compatibility mapping:

agentcore.json value Current behavior
omitted MCP-only
"MCP" MCP-only
"None" unrestricted; L3 omits the service field

The AgentCore service itself uses omission for an unrestricted Gateway and
explicit "MCP" for an MCP-only Gateway. The CLI contract should align:

agentcore.json value Desired behavior
omitted unrestricted
"MCP" MCP-only
"None" accepted as a legacy unrestricted value

The command experience should be:

# Unrestricted; protocolType omitted
agentcore add gateway --name tools

# MCP-only
agentcore add gateway --name tools --protocol-type MCP

This needs a coordinated compatibility migration. Existing schema-v1 projects
with omitted protocolType historically mean MCP, and imported MCP Gateways are
currently persisted with the field omitted. Those projects must not silently
become unrestricted when the L3 default changes.

This was intentionally deferred from aws/agentcore-cli#2028 so that PR can
preserve the currently published schema and L3 behavior.

Acceptance Criteria
  • Omitting --protocol-type in the old CLI persists no protocolType field and deploys an unrestricted Gateway.
  • --protocol-type MCP persists "protocolType": "MCP" and deploys an MCP-only Gateway.
  • The old CLI no longer needs customers to pass --protocol-type None; existing "None" project values remain valid.
  • Importing an MCP Gateway persists explicit "protocolType": "MCP".
  • Existing projects where omission historically meant MCP are migrated or normalized to explicit "MCP" before consuming the new L3 behavior.
  • The L3 treats omitted protocolType as unrestricted and explicit "MCP" as MCP-only.
  • Semantic-search protocol configuration remains usable on unrestricted Gateways when supported by the service.
  • The old CLI, project-based refactor, schema copies, generated CDK, and L3 tests use the same contract.
  • Release sequencing publishes the compatible L3 version before either CLI updates its exact L3 pin.
  • Regression tests prove existing MCP projects do not silently widen to unrestricted access.
Additional Context

This is a cross-repository compatibility change involving:

  • old CLI authoring, import, migration, generated CDK, and dependency pinning;
  • project-based refactor command and schema behavior;
  • aws/agentcore-l3-cdk-constructs schema and Gateway synthesis.
主要语言
TypeScript
星标
304
派生
105
平均合并
16 小时 14 分钟
30 天内合并 PR
186

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/agentcore-cli 的其他 Issue

查看 aws/agentcore-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。