feat(gateway-target): add --include-domains for the web-search connector

[sundargthb]

What

add gateway-target accepts --include-domains for the web-search connector, alongside the --exclude-domains it already had. The interactive wizard gains a matching Include Domains step, and the translator now emits both lists inside one domainFilter.

agentcore add gateway-target --type connector --connector web-search \
  --name ws --gateway main-gw \
  --include-domains docs.aws.amazon.com,aws.amazon.com \
  --exclude-domains internal.example.com

{ "name": "WebSearch", "parameterValues": { "domainFilter": {
  "include": ["docs.aws.amazon.com", "aws.amazon.com"],
  "exclude": ["internal.example.com"]
} } }

Why

The connector's admin-level domainFilter takes include and exclude, and the tool schema documents both. Both AgentCore SDKs expose both, per-request, and so does the tool itself. The CLI could only ever set exclude, so a target restricted to an approved set of domains was not expressible through the CLI at all, and the common case of pointing a search target at a documentation set had to be done by editing the project file by hand.

Behaviour worth knowing

An empty list is omitted rather than sent. An empty include is not the same request as an absent one: sending it would tell the connector to return nothing. Passing --include-domains "" therefore leaves the filter unset rather than producing a target that matches no domains.

--include-domains may be given once, with a comma-separated value, matching how --exclude-domains already behaves and reusing the same coercer. It is rejected on any target that is not --connector web-search, which is the existing gate generalised to cover both flags.

Tests

translators.ts had no test file, so this adds one covering include only, exclude only, both together, an empty list, and one list empty while the other is set. Two cases were added to GatewayTargetPrimitive.test.ts for the include path and for both lists reaching one domainFilter.

The unit suite is unchanged apart from those additions: 30 tests fail on main in this repo before this change and the same 30 fail after it, with 8 added tests passing. AddGatewayJwtConfig.test.tsx > confirm screen shows Allowed Audience value failed on one run and passed both in isolation and on a rerun, so that one is load-sensitive rather than related. Typecheck, eslint and prettier are clean.

[github-actions]

Package Tarball

aws-agentcore-0.28.1.tgz

How to install

gh release download pr-2269-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.28.1.tgz