mulesoft-anypoint-cli-agent-fabric-plugin 1.3.0 → 1.3.1-beta

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (184) hide show
  1. package/README.md +77 -42
  2. package/bin/run +6 -0
  3. package/dist/commands/agent-network/project/agent-console.d.ts +16 -0
  4. package/dist/commands/agent-network/project/agent-console.js +175 -0
  5. package/dist/commands/agent-network/project/agent-console.js.map +1 -0
  6. package/dist/commands/agent-network/project/broker/create.d.ts +10 -0
  7. package/dist/commands/agent-network/project/broker/create.js +192 -0
  8. package/dist/commands/agent-network/project/broker/create.js.map +1 -0
  9. package/dist/commands/agent-network/project/create.d.ts +12 -0
  10. package/dist/commands/agent-network/project/create.js +48 -11
  11. package/dist/commands/agent-network/project/create.js.map +1 -1
  12. package/dist/commands/agent-network/project/deploy.d.ts +24 -14
  13. package/dist/commands/agent-network/project/deploy.js +230 -178
  14. package/dist/commands/agent-network/project/deploy.js.map +1 -1
  15. package/dist/commands/agent-network/project/export-logs.d.ts +11 -0
  16. package/dist/commands/agent-network/project/export-logs.js +38 -0
  17. package/dist/commands/agent-network/project/export-logs.js.map +1 -0
  18. package/dist/commands/agent-network/project/mcp/introspect.js +4 -1
  19. package/dist/commands/agent-network/project/mcp/introspect.js.map +1 -1
  20. package/dist/commands/agent-network/project/publish.js +1 -1
  21. package/dist/commands/agent-network/project/publish.js.map +1 -1
  22. package/dist/commands/agent-network/project/run-local.d.ts +85 -0
  23. package/dist/commands/agent-network/project/run-local.js +825 -0
  24. package/dist/commands/agent-network/project/run-local.js.map +1 -0
  25. package/dist/commands/agent-network/project/secrets.d.ts +21 -0
  26. package/dist/commands/agent-network/project/secrets.js +163 -0
  27. package/dist/commands/agent-network/project/secrets.js.map +1 -0
  28. package/dist/commands/agent-network/project/stop-local.d.ts +11 -0
  29. package/dist/commands/agent-network/project/stop-local.js +38 -0
  30. package/dist/commands/agent-network/project/stop-local.js.map +1 -0
  31. package/dist/commands/agent-network/project/undeploy.js +15 -10
  32. package/dist/commands/agent-network/project/undeploy.js.map +1 -1
  33. package/dist/commands/agent-network/project/unpublish.js +14 -6
  34. package/dist/commands/agent-network/project/unpublish.js.map +1 -1
  35. package/dist/commands/agent-network/setup/gateways.d.ts +3 -0
  36. package/dist/commands/agent-network/setup/gateways.js +66 -3
  37. package/dist/commands/agent-network/setup/gateways.js.map +1 -1
  38. package/dist/errors/error-factory.d.ts +51 -6
  39. package/dist/errors/error-factory.js +246 -15
  40. package/dist/errors/error-factory.js.map +1 -1
  41. package/dist/helpers/proxy-agent.d.ts +2 -0
  42. package/dist/helpers/proxy-agent.js +26 -0
  43. package/dist/helpers/proxy-agent.js.map +1 -0
  44. package/dist/helpers/request-utils.d.ts +2 -1
  45. package/dist/helpers/request-utils.js +2 -2
  46. package/dist/helpers/request-utils.js.map +1 -1
  47. package/dist/helpers/utils.d.ts +1 -0
  48. package/dist/helpers/utils.js +5 -0
  49. package/dist/helpers/utils.js.map +1 -1
  50. package/dist/resources/agent-console.html +478 -0
  51. package/dist/resources/schemas/broker-deployment-settings.schema.json +46 -0
  52. package/dist/types/agent-network-v2.d.ts +4 -0
  53. package/dist/types/agent-network-v2.js.map +1 -1
  54. package/dist/types/types.d.ts +1 -0
  55. package/dist/utils/builders/network-lock.d.ts +1 -0
  56. package/dist/utils/builders/network-lock.js +41 -6
  57. package/dist/utils/builders/network-lock.js.map +1 -1
  58. package/dist/utils/builders/policies-factory.d.ts +5 -1
  59. package/dist/utils/builders/policies-factory.js +10 -2
  60. package/dist/utils/builders/policies-factory.js.map +1 -1
  61. package/dist/utils/builders/project-builder-impl.d.ts +16 -2
  62. package/dist/utils/builders/project-builder-impl.js +29 -1
  63. package/dist/utils/builders/project-builder-impl.js.map +1 -1
  64. package/dist/utils/builders/project-builder.d.ts +29 -2
  65. package/dist/utils/builders/project-builder.js +10 -2
  66. package/dist/utils/builders/project-builder.js.map +1 -1
  67. package/dist/utils/builders/remote-space-resolver.d.ts +2 -2
  68. package/dist/utils/builders/remote-space-resolver.js +27 -11
  69. package/dist/utils/builders/remote-space-resolver.js.map +1 -1
  70. package/dist/utils/builders/space-serializer.js +3 -1
  71. package/dist/utils/builders/space-serializer.js.map +1 -1
  72. package/dist/utils/builders/stage-diagnostics.d.ts +2 -0
  73. package/dist/utils/builders/stage-diagnostics.js +27 -0
  74. package/dist/utils/builders/stage-diagnostics.js.map +1 -0
  75. package/dist/utils/builders/tooling-metadata.d.ts +4 -4
  76. package/dist/utils/builders/tooling-metadata.js +27 -15
  77. package/dist/utils/builders/tooling-metadata.js.map +1 -1
  78. package/dist/utils/builders/v1/network-builder.js +2 -1
  79. package/dist/utils/builders/v1/network-builder.js.map +1 -1
  80. package/dist/utils/builders/v2/broker-builder.d.ts +1 -0
  81. package/dist/utils/builders/v2/broker-builder.js +69 -4
  82. package/dist/utils/builders/v2/broker-builder.js.map +1 -1
  83. package/dist/utils/builders/v2/network-builder.js +1 -1
  84. package/dist/utils/builders/v2/network-builder.js.map +1 -1
  85. package/dist/utils/constants.d.ts +3 -0
  86. package/dist/utils/constants.js +8 -3
  87. package/dist/utils/constants.js.map +1 -1
  88. package/dist/utils/deployment-settings.d.ts +13 -0
  89. package/dist/utils/deployment-settings.js +97 -0
  90. package/dist/utils/deployment-settings.js.map +1 -0
  91. package/dist/utils/facets/abstract-facet.d.ts +1 -0
  92. package/dist/utils/facets/abstract-facet.js +3 -0
  93. package/dist/utils/facets/abstract-facet.js.map +1 -1
  94. package/dist/utils/facets/agent-graph-facet.d.ts +14 -1
  95. package/dist/utils/facets/agent-graph-facet.js +126 -49
  96. package/dist/utils/facets/agent-graph-facet.js.map +1 -1
  97. package/dist/utils/facets/api-instance-facet.d.ts +36 -1
  98. package/dist/utils/facets/api-instance-facet.js +196 -5
  99. package/dist/utils/facets/api-instance-facet.js.map +1 -1
  100. package/dist/utils/facets/connection-facet.d.ts +8 -0
  101. package/dist/utils/facets/connection-facet.js +65 -1
  102. package/dist/utils/facets/connection-facet.js.map +1 -1
  103. package/dist/utils/facets/deployment-helpers.d.ts +18 -1
  104. package/dist/utils/facets/deployment-helpers.js +53 -0
  105. package/dist/utils/facets/deployment-helpers.js.map +1 -1
  106. package/dist/utils/facets/deployment-logs.js +1 -0
  107. package/dist/utils/facets/deployment-logs.js.map +1 -1
  108. package/dist/utils/facets/deployment-runner.js +5 -0
  109. package/dist/utils/facets/deployment-runner.js.map +1 -1
  110. package/dist/utils/facets/facets.d.ts +2 -0
  111. package/dist/utils/facets/facets.js +20 -3
  112. package/dist/utils/facets/facets.js.map +1 -1
  113. package/dist/utils/facets/mule-application-facet.d.ts +1 -1
  114. package/dist/utils/facets/mule-application-facet.js +25 -21
  115. package/dist/utils/facets/mule-application-facet.js.map +1 -1
  116. package/dist/utils/files.d.ts +25 -0
  117. package/dist/utils/files.js +62 -0
  118. package/dist/utils/files.js.map +1 -1
  119. package/dist/utils/gateway.d.ts +6 -2
  120. package/dist/utils/gateway.js +37 -33
  121. package/dist/utils/gateway.js.map +1 -1
  122. package/dist/utils/keychain.d.ts +56 -0
  123. package/dist/utils/keychain.js +488 -0
  124. package/dist/utils/keychain.js.map +1 -0
  125. package/dist/utils/logger.d.ts +1 -0
  126. package/dist/utils/logger.js +3 -0
  127. package/dist/utils/logger.js.map +1 -1
  128. package/dist/utils/mcp/mcp-metadata-mapper.d.ts +8 -0
  129. package/dist/utils/mcp/mcp-metadata-mapper.js +7 -1
  130. package/dist/utils/mcp/mcp-metadata-mapper.js.map +1 -1
  131. package/dist/utils/mcp/project-registrar.js +2 -26
  132. package/dist/utils/mcp/project-registrar.js.map +1 -1
  133. package/dist/utils/naming.d.ts +13 -0
  134. package/dist/utils/naming.js +36 -4
  135. package/dist/utils/naming.js.map +1 -1
  136. package/dist/utils/request-executor.d.ts +5 -5
  137. package/dist/utils/run-local/agent-console-proxy.d.ts +56 -0
  138. package/dist/utils/run-local/agent-console-proxy.js +182 -0
  139. package/dist/utils/run-local/agent-console-proxy.js.map +1 -0
  140. package/dist/utils/run-local/broker-recreate-selector.d.ts +31 -0
  141. package/dist/utils/run-local/broker-recreate-selector.js +82 -0
  142. package/dist/utils/run-local/broker-recreate-selector.js.map +1 -0
  143. package/dist/utils/run-local/build-status.d.ts +73 -0
  144. package/dist/utils/run-local/build-status.js +210 -0
  145. package/dist/utils/run-local/build-status.js.map +1 -0
  146. package/dist/utils/run-local/constants.d.ts +28 -0
  147. package/dist/utils/run-local/constants.js +36 -0
  148. package/dist/utils/run-local/constants.js.map +1 -0
  149. package/dist/utils/run-local/crd-files.d.ts +2 -0
  150. package/dist/utils/run-local/crd-files.js +24 -0
  151. package/dist/utils/run-local/crd-files.js.map +1 -0
  152. package/dist/utils/run-local/index.d.ts +9 -0
  153. package/dist/utils/run-local/index.js +42 -0
  154. package/dist/utils/run-local/index.js.map +1 -0
  155. package/dist/utils/run-local/local-a2a-upstream.d.ts +9 -0
  156. package/dist/utils/run-local/local-a2a-upstream.js +55 -0
  157. package/dist/utils/run-local/local-a2a-upstream.js.map +1 -0
  158. package/dist/utils/run-local/local-deploy-descriptor.d.ts +36 -0
  159. package/dist/utils/run-local/local-deploy-descriptor.js +70 -0
  160. package/dist/utils/run-local/local-deploy-descriptor.js.map +1 -0
  161. package/dist/utils/run-local/local-run-manager.d.ts +51 -0
  162. package/dist/utils/run-local/local-run-manager.js +220 -0
  163. package/dist/utils/run-local/local-run-manager.js.map +1 -0
  164. package/dist/utils/run-local/policy-resolver.d.ts +69 -0
  165. package/dist/utils/run-local/policy-resolver.js +461 -0
  166. package/dist/utils/run-local/policy-resolver.js.map +1 -0
  167. package/dist/utils/run-local/runtime-environment-manager.d.ts +89 -0
  168. package/dist/utils/run-local/runtime-environment-manager.js +313 -0
  169. package/dist/utils/run-local/runtime-environment-manager.js.map +1 -0
  170. package/dist/utils/run-local/secrets-manager.d.ts +66 -0
  171. package/dist/utils/run-local/secrets-manager.js +181 -0
  172. package/dist/utils/run-local/secrets-manager.js.map +1 -0
  173. package/dist/utils/uris.js +4 -0
  174. package/dist/utils/uris.js.map +1 -1
  175. package/dist/utils/variables.d.ts +17 -4
  176. package/dist/utils/variables.js +52 -7
  177. package/dist/utils/variables.js.map +1 -1
  178. package/package.json +3 -1
  179. package/scripts/check-gus-ticket-format.sh +29 -0
  180. package/scripts/resolve-version.sh +161 -52
  181. package/scripts/resolve-version.test.sh +207 -20
  182. package/templates/agent-network/exchange.json.template +1 -0
  183. package/templates/agentic-network/brokers/broker1.agent.template +2 -2
  184. package/templates/agentic-network/exchange.json.template +1 -0
@@ -17,29 +17,100 @@ RESOLVER="${SCRIPT_DIR}/resolve-version.sh"
17
17
  fail=0
18
18
  pass=0
19
19
 
20
+ # Builds a fake `npm` executable that fails `npm view` with the given
21
+ # stderr output, so published_versions()'s registry-failure path can be
22
+ # exercised deterministically and offline (no real network/registry).
23
+ make_fake_npm() {
24
+ local bindir="$1" stderr_output="$2"
25
+ mkdir -p "$bindir"
26
+ cat > "${bindir}/npm" <<SCRIPT
27
+ #!/usr/bin/env bash
28
+ echo "${stderr_output}" >&2
29
+ exit 1
30
+ SCRIPT
31
+ chmod +x "${bindir}/npm"
32
+ }
33
+
34
+ # Builds a fake `npm` executable that SUCCEEDS (exit 0) with the given stdout
35
+ # JSON, but ALSO writes noise to stderr -- reproducing real npm@10.8.3's
36
+ # "npm info using npm@10.8.3" banner on stderr on every call, success or not.
37
+ make_fake_npm_success() {
38
+ local bindir="$1" stdout_json="$2" stderr_noise="$3"
39
+ mkdir -p "$bindir"
40
+ cat > "${bindir}/npm" <<SCRIPT
41
+ #!/usr/bin/env bash
42
+ echo "${stderr_noise}" >&2
43
+ echo '${stdout_json}'
44
+ exit 0
45
+ SCRIPT
46
+ chmod +x "${bindir}/npm"
47
+ }
48
+
20
49
  run_case() {
21
50
  local label="$1"; shift
22
51
  local expected="$1"; shift
23
- # Remaining args are VAR=VALUE pairs to export for the resolver.
52
+ # Remaining args are VAR=VALUE pairs to export for the resolver, plus
53
+ # test-only directives consumed here (not exported): PKG_VERSION=x.y.z
54
+ # overrides the fixture's package.json version (default 1.0.0);
55
+ # FAKE_NPM_STDERR=<text> puts a fake FAILING `npm` on PATH instead of
56
+ # relying on RESOLVE_PUBLISHED_VERSIONS_JSON; FAKE_NPM_SUCCESS_JSON=<json>
57
+ # (paired with FAKE_NPM_NOISE=<text>) puts a fake SUCCEEDING `npm` on
58
+ # PATH that also writes noise to stderr, reproducing real npm's
59
+ # informational banners on a successful call; PRE_TAG=<tag> creates that
60
+ # git tag in the fixture BEFORE the resolver runs, to simulate "a prior
61
+ # build already tagged this version, but the registry doesn't know it
62
+ # yet" (git_tag_versions()'s reason for existing).
63
+
64
+ local pkg_version="1.0.0"
65
+ local fake_npm_stderr=""
66
+ local fake_npm_success_json=""
67
+ local fake_npm_noise=""
68
+ local pre_tag=""
69
+ local -a envs=()
70
+ for kv in "$@"; do
71
+ case "$kv" in
72
+ PKG_VERSION=*) pkg_version="${kv#PKG_VERSION=}" ;;
73
+ FAKE_NPM_STDERR=*) fake_npm_stderr="${kv#FAKE_NPM_STDERR=}" ;;
74
+ FAKE_NPM_SUCCESS_JSON=*) fake_npm_success_json="${kv#FAKE_NPM_SUCCESS_JSON=}" ;;
75
+ FAKE_NPM_NOISE=*) fake_npm_noise="${kv#FAKE_NPM_NOISE=}" ;;
76
+ PRE_TAG=*) pre_tag="${kv#PRE_TAG=}" ;;
77
+ *) envs+=("$kv") ;;
78
+ esac
79
+ done
24
80
 
25
81
  local tmpdir
26
82
  tmpdir="$(mktemp -d)"
27
83
  trap 'rm -rf "$tmpdir"' RETURN
28
84
 
29
- cat > "${tmpdir}/package.json" <<'JSON'
85
+ cat > "${tmpdir}/package.json" <<JSON
30
86
  {
31
87
  "name": "@mulesoft/anypoint-cli-agent-fabric-plugin",
32
- "version": "1.0.0",
88
+ "version": "${pkg_version}",
33
89
  "description": "agent-fabric plugin"
34
90
  }
35
91
  JSON
92
+ git -C "$tmpdir" init -q
93
+ git -C "$tmpdir" config user.email "test@example.com"
94
+ git -C "$tmpdir" config user.name "test"
95
+ git -C "$tmpdir" add package.json
96
+ git -C "$tmpdir" commit -q -m init
97
+ if [[ -n "$pre_tag" ]]; then
98
+ git -C "$tmpdir" tag "$pre_tag"
99
+ fi
36
100
 
37
101
  (
38
102
  cd "$tmpdir"
39
103
  unset BRANCH_NAME GIT_BRANCH BUILD_NUMBER
40
- for kv in "$@"; do
104
+ for kv in "${envs[@]}"; do
41
105
  export "$kv"
42
106
  done
107
+ if [[ -n "$fake_npm_stderr" ]]; then
108
+ make_fake_npm "${tmpdir}/bin" "$fake_npm_stderr"
109
+ export PATH="${tmpdir}/bin:${PATH}"
110
+ elif [[ -n "$fake_npm_success_json" ]]; then
111
+ make_fake_npm_success "${tmpdir}/bin" "$fake_npm_success_json" "$fake_npm_noise"
112
+ export PATH="${tmpdir}/bin:${PATH}"
113
+ fi
43
114
  "$RESOLVER" > /dev/null
44
115
  )
45
116
 
@@ -60,29 +131,145 @@ JSON
60
131
  trap - RETURN
61
132
  }
62
133
 
134
+ # Asserts the resolver ABORTS (non-zero exit) instead of writing a version --
135
+ # used for the registry-failure-that-is-not-a-404 path, where publishing a
136
+ # silently-re-derived version would be worse than failing the build.
137
+ run_fail_case() {
138
+ local label="$1"; shift
139
+ local fake_npm_stderr="$1"; shift
140
+ # Remaining args are VAR=VALUE pairs to export for the resolver.
141
+
142
+ local tmpdir
143
+ tmpdir="$(mktemp -d)"
144
+ trap 'rm -rf "$tmpdir"' RETURN
145
+
146
+ cat > "${tmpdir}/package.json" <<'JSON'
147
+ {
148
+ "name": "@mulesoft/anypoint-cli-agent-fabric-plugin",
149
+ "version": "1.0.0",
150
+ "description": "agent-fabric plugin"
151
+ }
152
+ JSON
153
+ make_fake_npm "${tmpdir}/bin" "$fake_npm_stderr"
154
+
155
+ local rc=0
156
+ (
157
+ cd "$tmpdir"
158
+ unset BRANCH_NAME GIT_BRANCH BUILD_NUMBER RESOLVE_PUBLISHED_VERSIONS_JSON
159
+ for kv in "$@"; do
160
+ export "$kv"
161
+ done
162
+ export PATH="${tmpdir}/bin:${PATH}"
163
+ "$RESOLVER" > /dev/null 2>/dev/null
164
+ ) || rc=$?
165
+
166
+ if [[ "$rc" -ne 0 ]]; then
167
+ echo " ok ${label}: resolver aborted (exit ${rc}) as expected"
168
+ pass=$((pass + 1))
169
+ else
170
+ echo " FAIL ${label}: expected resolver to abort, but it exited 0" >&2
171
+ fail=$((fail + 1))
172
+ fi
173
+
174
+ rm -rf "$tmpdir"
175
+ trap - RETURN
176
+ }
177
+
63
178
  echo "resolve-version.sh integration tests"
64
179
 
65
180
  # master derives its patch from the published-versions list (injected offline),
66
181
  # not from package.json's patch or BUILD_NUMBER.
67
182
  VERS_10='["1.0.0","1.0.1-arroba-mulesoft-added.1","1.0.2-19.sfci-mig-plan-b-4","1.0.6-7.arroba-mulesoft-added","1.1.0"]'
68
183
 
69
- run_case "master -> next patch above all 1.0.x" "1.0.7" "BRANCH_NAME=master" "BUILD_NUMBER=42" "RESOLVE_PUBLISHED_VERSIONS_JSON=${VERS_10}"
70
- run_case "master -> 1.0.1 when only 1.0.0 clean" "1.0.1" "BRANCH_NAME=master" "BUILD_NUMBER=42" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.0\"]"
71
- run_case "master -> 1.0.0 when none published" "1.0.0" "BRANCH_NAME=master" "BUILD_NUMBER=42" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
184
+ run_case "master -> next patch above all 1.0.x" "1.0.7" "BRANCH_NAME=master" "RESOLVE_PUBLISHED_VERSIONS_JSON=${VERS_10}"
185
+ run_case "master -> 1.0.1 when only 1.0.0 clean" "1.0.1" "BRANCH_NAME=master" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.0\"]"
186
+ run_case "master -> 1.0.0 when none published" "1.0.0" "BRANCH_NAME=master" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
72
187
  run_case "master patch ignores BUILD_NUMBER" "1.0.7" "BRANCH_NAME=master" "BUILD_NUMBER=999" "RESOLVE_PUBLISHED_VERSIONS_JSON=${VERS_10}"
73
- run_case "test/* branch -> prerelease" "1.0.0-sfci-mig-plan-b.7" "BRANCH_NAME=test/sfci-mig-plan-b" "BUILD_NUMBER=7"
74
- run_case "origin/ prefix stripped" "1.0.0-my-branch.3" "BRANCH_NAME=origin/my-branch" "BUILD_NUMBER=3"
75
- run_case "GIT_BRANCH fallback" "1.0.0-x.11" "GIT_BRANCH=feature/x" "BUILD_NUMBER=11"
76
-
77
- # release/* branches produce a CLEAN stable version (no prerelease suffix),
78
- # same registry-derived patch rule as master.
79
- run_case "release/ pins branch major.minor" "1.3.0" "BRANCH_NAME=release/1.3" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
80
- run_case "release/ next patch above published" "1.3.3" "BRANCH_NAME=release/1.3" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.3.0\",\"1.3.2\"]"
81
- run_case "release/x.y.z pins major.minor only" "1.3.3" "BRANCH_NAME=release/1.3.9" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.3.2\"]"
82
- run_case "release/ origin prefix stripped" "1.3.0" "BRANCH_NAME=origin/release/1.3" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
83
- run_case "release/ no version -> pkg.json m.m" "1.0.1" "BRANCH_NAME=release/hardening" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.0\"]"
84
- run_case "release/v-prefix pins major.minor" "2.5.0" "BRANCH_NAME=release/v2.5" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
85
- run_case "release/ bare major -> M.0" "3.0.0" "BRANCH_NAME=release/3" "BUILD_NUMBER=5" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
188
+
189
+ # Non-master production branches (test/*, develop, feature/*, release/*) get
190
+ # a pre-release with their OWN patch counter: starts at package.json's base
191
+ # patch (1.0.0 -> patch 0) when nothing is published for that branch yet,
192
+ # then increments per build of that same branch -- BUILD_NUMBER is ignored.
193
+ # The FULL branch path (every segment, not just the last) becomes the
194
+ # identifier, so different branch TYPES never share one prerelease lineage.
195
+ run_case "test/* branch -> starts at base patch" "1.0.0-test-sfci-mig-plan-b" "BRANCH_NAME=test/sfci-mig-plan-b" "BUILD_NUMBER=7" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
196
+ run_case "test/* branch -> increments on 2nd build" "1.0.1-test-sfci-mig-plan-b" "BRANCH_NAME=test/sfci-mig-plan-b" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.0-test-sfci-mig-plan-b\"]"
197
+ run_case "test/* branch ignores BUILD_NUMBER" "1.0.0-test-sfci-mig-plan-b" "BRANCH_NAME=test/sfci-mig-plan-b" "BUILD_NUMBER=999" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
198
+ run_case "other branch's counter does not interfere" "1.0.0-other-branch" "BRANCH_NAME=other-branch" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.5-test-sfci-mig-plan-b\"]"
199
+ run_case "origin/ prefix stripped (no other segment)" "1.0.0-my-branch" "BRANCH_NAME=origin/my-branch" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
200
+ run_case "GIT_BRANCH fallback keeps its segment" "1.0.0-feature-x" "GIT_BRANCH=feature/x" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
201
+
202
+ # release/* is just another production branch now (only master cuts a clean
203
+ # semver release) -> per-branch pre-release counter, same as test/*/feature/*.
204
+ run_case "release/ branch -> starts at base patch" "1.0.0-release-1.3" "BRANCH_NAME=release/1.3" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
205
+ run_case "release/ branch -> increments on 2nd build" "1.0.1-release-1.3" "BRANCH_NAME=release/1.3" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.0.0-release-1.3\"]"
206
+ run_case "release/ origin prefix stripped" "1.0.0-release-1.3" "BRANCH_NAME=origin/release/1.3" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
207
+
208
+ # Regression coverage for the production collision this fix corrects: before
209
+ # it, release/1.2.25-2 and test/1.2.25-2 (and a nested test/release/1-2-25-2)
210
+ # all published the SAME version (1.2.25-1-2-25-2), because only the last
211
+ # path segment was kept. Each branch TYPE now gets a distinct lineage. Dots
212
+ # inside a segment are kept literally (not collapsed to dashes) -- only the
213
+ # `/` path separator becomes `-`.
214
+ run_case "release/1.2.25-2 keeps the release- type prefix and its dots" "1.2.25-release-1.2.25-2" "BRANCH_NAME=release/1.2.25-2" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
215
+ run_case "release/1.2.25-2 2nd build increments its own lineage" "1.2.26-release-1.2.25-2" "BRANCH_NAME=release/1.2.25-2" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-release-1.2.25-2\"]"
216
+ run_case "test/1.2.25-2 gets a DIFFERENT lineage than release/" "1.2.25-test-1.2.25-2" "BRANCH_NAME=test/1.2.25-2" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-release-1.2.25-2\"]"
217
+ run_case "test/1.2.25-2 2nd build increments its own lineage" "1.2.26-test-1.2.25-2" "BRANCH_NAME=test/1.2.25-2" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-test-1.2.25-2\"]"
218
+ run_case "nested test/release/1-2-25-2 keeps both segments" "1.2.25-test-release-1-2-25-2" "BRANCH_NAME=test/release/1-2-25-2" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
219
+
220
+ # Regression coverage for the SECOND production bug: release/1.2.25-hf ran
221
+ # two builds 28 minutes apart and published the exact same version both
222
+ # times. Build 2's own log proved the git tag from build 1 was already
223
+ # present ("could not create tag, already exists") -- npm view alone (via
224
+ # RESOLVE_PUBLISHED_VERSIONS_JSON=[] here, simulating the Nexus-proxy lag
225
+ # that made it blind to a version published minutes earlier) is no longer
226
+ # the only signal: a pre-existing git tag for that exact version must still
227
+ # push the counter forward instead of colliding with it.
228
+ run_case "pre-existing git tag advances the counter past a stale npm view" "1.2.26-release-1.2.25-hf" "BRANCH_NAME=release/1.2.25-hf" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]" "PRE_TAG=1.2.25-release-1.2.25-hf"
229
+
230
+ # The per-branch counter starts at package.json's OWN current patch, which
231
+ # is only meaningfully exercised at a non-zero patch (every case above uses
232
+ # fixture version 1.0.0, so the floor is always 0) -- matches production,
233
+ # which is already at 1.2.25.
234
+ run_case "branch counter starts at package.json's non-zero patch" "1.2.25-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
235
+ run_case "branch counter increments above non-zero base" "1.2.26-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-test-develop\"]"
236
+
237
+ # Legacy pre-migration versions (MAJOR.MINOR.PATCH-BRANCH.BUILD, published by
238
+ # the old BUILD_NUMBER scheme) must still count toward the branch's max patch
239
+ # -- otherwise the first post-migration build of a long-lived branch resets
240
+ # to the floor, which is a semver REGRESSION relative to the legacy tag
241
+ # (fewer pre-release fields = lower precedence at equal PATCH).
242
+ run_case "legacy .BUILD-suffixed version still counts toward max" "1.2.26-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-test-develop.1\"]"
243
+ run_case "legacy + new-format versions: max wins across both" "1.2.28-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "RESOLVE_PUBLISHED_VERSIONS_JSON=[\"1.2.25-test-develop.1\",\"1.2.27-test-develop\"]"
244
+
245
+ # A branch name that normalizes to pure digits with no other path segment
246
+ # (e.g. a bare branch called `007`, no slash) would be an invalid semver
247
+ # identifier (numeric identifiers can't have a leading zero, and a bare
248
+ # numeric tail is easy to misread as a version) -- it must come out
249
+ # alphanumeric. A prefixed branch like release/1.3 is unaffected: it already
250
+ # contains the "release" segment, so it was never purely numeric.
251
+ run_case "bare numeric branch (leading zero) gets a non-numeric prefix" "1.0.0-b007" "BRANCH_NAME=007" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
252
+ run_case "bare numeric branch (no leading zero) still gets prefixed" "1.0.0-b42" "BRANCH_NAME=42" "RESOLVE_PUBLISHED_VERSIONS_JSON=[]"
253
+
254
+ # A registry error that ISN'T a 404 (network/auth/outage) must abort the
255
+ # build rather than being treated as "nothing published yet" -- silently
256
+ # re-deriving the floor version when one is already published would fail
257
+ # npm-publish on a duplicate, or worse, look like a fresh build that isn't.
258
+ run_fail_case "npm view non-404 failure aborts the build" "npm ERR! network timeout ECONNRESET" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25"
259
+
260
+ # A genuine 404 (brand-new/unpublished package) IS treated as "nothing
261
+ # published yet" -- this is the legitimate empty case the fallback exists for.
262
+ run_case "npm view 404 (new package) is treated as empty" "1.2.25-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "FAKE_NPM_STDERR=npm ERR! 404 Not Found - GET https://registry/@mulesoft%2fanypoint-cli-agent-fabric-plugin - Not found E404"
263
+
264
+ # Regression coverage for the THIRD production bug: real npm (confirmed
265
+ # npm@10.8.3) writes an informational banner ("npm info using npm@10.8.3")
266
+ # to stderr on every call, success or not. published_versions() used to
267
+ # merge stdout+stderr via `2>&1`, so that banner got prepended to the JSON
268
+ # payload on the SUCCESS path too, corrupting JSON.parse and hard-failing
269
+ # EVERY branch build (confirmed: test/W-23849126-3-sfci-version's Package
270
+ # stage failed with exactly this SyntaxError). stdout and stderr must stay
271
+ # separate: a successful call's noisy stderr must never affect its result.
272
+ run_case "npm view success + stderr noise doesn't corrupt the JSON payload" "1.2.26-test-develop" "BRANCH_NAME=test/develop" "PKG_VERSION=1.2.25" "FAKE_NPM_SUCCESS_JSON=[\"1.2.25-test-develop\"]" "FAKE_NPM_NOISE=npm info using npm@10.8.3"
86
273
 
87
274
  if [[ "$fail" -gt 0 ]]; then
88
275
  echo "resolve-version.sh: ${pass} passed, ${fail} failed" >&2
@@ -11,6 +11,7 @@
11
11
  "version": "{{assetVersion}}",
12
12
  "dependencies": [],
13
13
  "metadata": {
14
+ "toolingVersion": 1,
14
15
  "variables": {
15
16
  "agent1": {
16
17
  "url": {
@@ -3,7 +3,7 @@ system:
3
3
  instructions: "You are a helpful assistant."
4
4
 
5
5
  config:
6
- agent_name: "My Broker 1"
6
+ agent_name: "{{brokerName}}"
7
7
  default_llm: @llm.openai_llm
8
8
 
9
9
  llm:
@@ -27,7 +27,7 @@ actions:
27
27
 
28
28
  trigger brokerTrigger:
29
29
  kind: "a2a"
30
- target: "brokers://broker1/a2a"
30
+ target: "brokers://{{brokerId}}/a2a"
31
31
  on_message: ->
32
32
  transition to @orchestrator.main
33
33
 
@@ -11,6 +11,7 @@
11
11
  "version": "{{assetVersion}}",
12
12
  "dependencies": [],
13
13
  "metadata": {
14
+ "toolingVersion": 1,
14
15
  "variables": {
15
16
  "myAgent": {
16
17
  "url": {