@cap-js-community/mtx-tool 0.13.0

v0.13.0

on Node.js NPM

We reworked the service-manager interactions. The operations for credential rotation become idempotent now, making
outside retries possible.

The old commands still work but are now deprecated: they emit a warning and delegate to the new implementations. Migrate to the replacements below, as the deprecated commands will be removed in a future release.

The full rotation is a five-step choreography of the two idempotent commands:

1. rolling restart — converge apps onto the most-recent binding.
2. --svm-make-bindings-single — prune to one binding per instance.
3. --svm-make-bindings-double — add the new binding.
4. rolling restart — apps switch to the new binding.
5. --svm-make-bindings-single — prune the old binding.

If the fleet is already at one binding per instance, skip to step 3.

CHANGED

• npm: use bundleDependencies instead of shrinkwrap to ship the whatwg-url override to users. shrinkwrap is no
  longer honored as of npm v12.

• svm: reworked --svm-repair-bindings to --svm-make-bindings-single and --svm-fresh-bindings to
  --svm-make-bindings-double. both are now idempotent and have the SERVICE_PLAN TENANT_ID calling args, making
  them consistent with other svm commands.

• svm: --svm-repair-bindings, --svm-fresh-bindings, and --svm-refresh-bindings are deprecated. they still work
  but now emit a warning. they are reimplemented on top of the new idempotent binding logic in a way that reproduces
  their previous behavior, and will be removed in a future release. migrate to --svm-make-bindings-single,
  --svm-make-bindings-double.

FIXED

• reg: subscription listing now uses the cursor-based paging APIs (/subscription-manager/v2/subscriptions and
  /saas-manager/v2/application/subscriptions) instead of page-number paging, keeping pagination reliable for large
  result sets (fixes #197).

• core: mtx cache now dedupes concurrent lookups of the same configured app name, avoiding redundant cf requests.