@varde-flyt/vfac 0.18.0 → 0.18.1

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.
package/README.md CHANGED
@@ -253,6 +253,12 @@ file that turns the setting off. A released connection is torn down by its
253
253
  provider afterwards, and the providing resource can only be deleted once that
254
254
  teardown is done.
255
255
 
256
+ **Two resources connected to each other hold each other**: each is the other's
257
+ provider, so both deletes are refused. Break the loop at one link — set one of
258
+ the two connections to `state: disconnected` and apply, wait until its teardown
259
+ is done, delete the resource nothing holds any more, and delete the other once
260
+ that deletion has finished.
261
+
256
262
  **A manifest never moves a connection in one apply**: pointing an existing
257
263
  connection at a different resource is refused rather than performed, because a
258
264
  file you re-apply on every push must not be able to silently move a running
package/dist/vfac.mjs CHANGED
@@ -19188,7 +19188,7 @@ function renderOperation(operationId, data) {
19188
19188
  const cause2 = failure["cause"];
19189
19189
  const named = reportedSettings[0];
19190
19190
  lines.push(
19191
- retryable ? ` Another attempt can succeed: ${again}.` : named !== void 0 ? ` Correct \`${named}\` in your manifest, then \`vfac apply\` it${data["type"] === "PRODUCT_INSTANCE_UPGRADE" ? ` and ${again}` : ""}. Repeating it unchanged fails the same way.` : cause2 === "unknown" ? ` The platform could not classify this, so there is nothing here to correct. Read the whole record with \`vfac get operation ${operationId} --output json\`, and quote that id if you ask for help. Repeating it unchanged fails the same way.` : ` Repeating this unchanged fails again \u2014 fix what the lines above name, then ${again}${changeIt}.`
19191
+ named !== void 0 ? ` Correct \`${named}\` in your manifest, then \`vfac apply\` it${data["type"] === "PRODUCT_INSTANCE_UPGRADE" ? ` and ${again}` : ""}. Repeating it unchanged fails the same way.` : retryable ? ` Another attempt can succeed: ${again}.` : cause2 === "unknown" ? ` The platform could not classify this, so there is nothing here to correct. Read the whole record with \`vfac get operation ${operationId} --output json\`, and quote that id if you ask for help. Repeating it unchanged fails the same way.` : ` Repeating this unchanged fails again \u2014 fix what the lines above name, then ${again}${changeIt}.`
19192
19192
  );
19193
19193
  }
19194
19194
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@varde-flyt/vfac",
3
- "version": "0.18.0",
3
+ "version": "0.18.1",
4
4
  "description": "Deploy and manage Varde Flyt Products from a manifest.",
5
5
  "repository": {
6
6
  "type": "git",