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

project deploy cannot create payment credential providers; support Quick Create connectors first

未关闭
#2,095 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

从 src/projectSchemas/payment.ts 和 src/assets/cdk/lib/cdk-stack.ts 开始,然后检查 agentcore project add credentials 背后的支付凭据和连接器流程。确认每个受支持的供应商是否都提供 Quick Create,定义 authorizationUrl 和凭据创建应如何工作,并验证 agentcore project deploy 能够处理所选路径,而不会拒绝支付连接器。

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

描述

Summary

agentcore project deploy refuses any project declaring a PaymentCredentialProvider credential:

Error: Credential 'my-pay' is a PaymentCredentialProvider, which 'agentcore project deploy'
cannot create: CloudFormation has no payment credential provider resource, and a payment
provider needs vendor configuration (API key, wallet and authorization secrets) that
agentcore.json has no fields for. Remove the credential and any payment connector referencing
it to deploy the rest of the project.

That is deliberate — see #2089, which moved credential providers into CloudFormation. Failing fast beats half-creating a provider. This issue is the follow-up to actually support payments under project deploy.

A payment credential can only reach agentcore.json by hand today: agentcore project add credentials offers only api-key and oauth. So no documented flow produces this error yet.

Two paths, and the cheap one is already released

Quick Create — needs no credential provider at all

agentcore-l3-cdk-constructs#324 ("feat(payments): support Quick Create connectors") is on the L3's main and shipped in 0.1.0-alpha.49. A Quick Create connector needs no credentialProviderArn — the customer completes authorization out of band via a returned URL.

This is the path to do first. It closes the common case without touching the credential schema at all:

  • make credentialName optional in src/projectSchemas/payment.ts
  • add a Quick Create connector variant to the spec
  • surface the returned authorizationUrl so the user knows how to finish setup
  • src/assets/cdk/lib/cdk-stack.ts skips the credential-map lookup for those connectors

Unverified: whether Quick Create is Coinbase-specific. If StripePrivy has no Quick Create equivalent, it still needs the Manual path below. Confirm before scoping.

Manual — needs real work

The Manual path is what the fail-fast message describes, and the gap is genuine:

  1. No CloudFormation resource. Unlike ApiKeyCredentialProvider and OAuth2CredentialProvider, there is no payment credential provider type usable from the stack, so the pattern #2089 established (CFN owns the provider, the CLI syncs the secret post-deploy) does not apply.

  2. PaymentCredentialSchema has nowhere to put vendor configuration. It carries only {authorizerType, name, provider}. The API wants vendor identifiers and secrets:

    • CoinbaseCDP: API key ID + secret, wallet secret
    • StripePrivy: app ID, authorization ID, and their secrets

    The non-secret identifiers need schema fields. The secrets need the same .env.local-or-secretRef story the other two credential kinds have, which means extending credentialEnvVarName beyond its current one-suffix shape (_CLIENT_SECRET) to several per credential.

Also worth deciding here

agentcore project add credentials payment does not exist. Whichever path lands, the credential should be creatable without hand-editing agentcore.json.

Related

  • #2089 — moves credential providers into CloudFormation; adds the fail-fast this issue removes
  • #2093 — the original credential-deploy issue and its remaining open items
主要语言
TypeScript
星标
291
派生
96
平均合并
17 小时 29 分钟
30 天内合并 PR
193

环境准备

从这里开始

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

aws/agentcore-cli 的其他 Issue

查看 aws/agentcore-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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