Remove snake_case-only restriction on connection & broker IDs; update deploy gateway model - #209
Merged
Conversation
… deploy gateway model The V2 schema does not restrict connection ids or broker ids to ^[a-z0-9_]+$ — any valid YAML identifier validates (camelCase, snake_case, kebab-case). Both Agent Broker skills previously claimed this was schema-enforced and that other casings 'fail lint'; that was incorrect. The skills now frame snake_case as a readability convention and keep the one real invariant: .agent targets must match the agent-network.yaml keys exactly. Also updates the builder's Step 9 deploy guidance to the CLI plugin v1.2.10 gateway model: single-gateway mode (-g/--gateway, default agent-network-gw) recommended, separate ingress/egress (-i/-e) as the alternate mode. Bumps skill package version 1.8.3 -> 1.8.4 with CHANGELOG entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
spezzirriemiliano
approved these changes
Aug 11, 2026
spezzirriemiliano
left a comment
spezzirriemiliano
left a comment
Contributor
There was a problem hiding this comment.
Corrects an inaccurate schema-restriction claim (connection/broker IDs are not snake_case-restricted) and updates stale gateway deploy defaults across two prose skills, with a consistent version bump and CHANGELOG entry; no validator failures or blockers found.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Corrects two things in the Agent Broker skills (
build-agent-broker-project,translate-agent-broker-old-to-new-project):1. Connection & broker id naming (bug fix)
Both skills claimed the V2 schema restricts
context.connections.<id>keys andbrokers.<id>keys to^[a-z0-9_]+$(snake_case only) and that camelCase/kebab-case "fails lint." This is incorrect — the schema accepts any valid YAML identifier. The 2.0 docs corroborate this (registry keys allow^[a-zA-Z_][a-zA-Z0-9_.-]*$, and the Agent Script reference's own trigger example uses a kebab-case broker:brokers://employee-onboarding/a2a).The skills now:
.agenttarget (a2a://,mcp://,llm://,brokers://) must match itsagent-network.yamlkey exactly.Touched:
canonical-example.mditem 0,gotchas.mdnaming conventions, converterSKILL.md,v2-template.agentcomments,v2-example.mdannotations.2. Deploy gateway model (update)
gotchas.mdStep 9 documented only the old separate-gateway defaults (agent-network-ingress-gw/agent-network-egress-gw). Updated to the current Anypoint CLI Agent Fabric plugin v1.2.10 model: single-gateway mode (-g/--gateway, defaultagent-network-gw) is recommended; separate ingress/egress (-i/-e) is the alternate mode.Version
Bumps
@salesforce/mulesoft-vibes-skills1.8.3 → 1.8.4 with CHANGELOG entry.Verification
mulesoft/docs-code-builder@latest) and the public npm CLI README (v1.2.10).🤖 Generated with Claude Code