@varde-flyt/vfac 0.12.0 → 0.14.0

package/README.md

@@ -80,8 +80,18 @@ vfac get operation <operationId>
 vfac get product-instance <productInstanceId>
 ```
 
+Lost the operation id — a terminal that closed, a CI log nobody kept? The
+operations of a resource are listed newest first, one page at a time; the
+`--cursor` for older ones is printed, and is `nextCursor` in JSON:
+
+```sh
+vfac get operations --resource <productInstanceId>
+```
+
 Secrets are supplied per apply and never belong in the manifest — a manifest is a
-file you commit. **Plan the run that sets one with the same `--secret` inputs the
+file you commit. A value for a setting the Product declares secret is refused
+at every door by the platform, and by `vfac` before the file is sent when the
+file pins the release the catalog currently offers. **Plan the run that sets one with the same `--secret` inputs the
 apply will carry**: `plan` takes the flag exactly as `apply` does, and without it
 the plan describes a different request.
 
@@ -182,7 +192,9 @@ spec:
 
 `vfac manifest init` names the exact property for every dependency you have to
 choose, and `vfac plan` prints the connections an apply would establish before
-you approve it. The dependency key comes from the Product, not from you —
+you approve it. A resource in this Project that cannot provide the connection is
+refused on `spec.dependencyBindings.<dependency-key>`, saying why; one named in
+another Project answers only that it could not be used. The dependency key comes from the Product, not from you —
 `vfac product show <productId>` lists every dependency with its key, its
 capability, and whether a setting is what turns it on.
 
@@ -214,6 +226,7 @@ vfac product show <productId> --output json
 vfac plan -f resource.yaml --output json
 vfac get product-instance <productInstanceId> --output json
 vfac get product-instances --output json
+vfac get operations --resource <productInstanceId> --output json
 ```
 
 **Decide from the action, not from the exit code.** A plan that REFUSES still
@@ -235,8 +248,9 @@ The envelopes are stable at the top level:
 
 | Command | Answers with |
 | --- | --- |
-| `vfac get product-instance <id> --output json` | `resource` and `lifecycle` — `status`, `outputs` and `conditions` are under `resource` |
+| `vfac get product-instance <id> --output json` | `resource` and `lifecycle` — `status`, `outputs` and `conditions` are under `resource`; each condition carries `state` and `freshness` (`FRESH`, or `STALE` when not re-confirmed recently), and `lifecycle.refused[]` carries a `reason` |
 | `vfac get product-instances --output json` | `productInstances` and `nextCursor` |
+| `vfac get operations --resource <productInstanceId> --output json` | `operations` and `nextCursor` — one page, newest first, and `nextCursor` reads older ones; each line is `operationId`, `type`, `status`, `phase` and its timestamps |
 
 `vfac guide` is authoritative for what is inside them.