@klok-integration/cli 0.7.283 → 0.7.288
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.
|
@@ -232,7 +232,7 @@ List tasks in the tenant
|
|
|
232
232
|
| Option | Description |
|
|
233
233
|
|---|---|
|
|
234
234
|
| `--status <status>` | submitted \| working \| input-required \| completed \| failed \| canceled |
|
|
235
|
-
| `--type <taskType>` | landscape-question \| impact-analysis \| integration-plan \| erp-change-plan \| issue-creation \| bead-creation \| project-scaffold \| datamodel-proposal \| repo-index \| bead-implementation |
|
|
235
|
+
| `--type <taskType>` | landscape-question \| impact-analysis \| integration-plan \| erp-change-plan \| issue-creation \| bead-creation \| project-scaffold \| datamodel-proposal \| repo-index \| bead-implementation \| build-check \| datamodel-upgrade \| pipeline-fix \| merge-conflict |
|
|
236
236
|
| `--limit <n>` | Maximum number of tasks (default: `50`) |
|
|
237
237
|
|
|
238
238
|
### klok agent open
|
|
@@ -52,6 +52,12 @@ domains read should still travel as class B or C (transform at the edge).
|
|
|
52
52
|
Vault needs nothing per project: the tenant CI role `<tenant>-ci` accepts every project under the tenant's
|
|
53
53
|
root group. If `publish_java_projects` fails at `auth/jwt/login`, the tenant itself is not set up; see the
|
|
54
54
|
`klok-release` skill.
|
|
55
|
+
|
|
56
|
+
GitLab does need one setting per project: the tenant's root group on the project's CI job token allowlist
|
|
57
|
+
(*Settings → CI/CD → Job token permissions*, or `POST /projects/<numeric id>/job_token_scope/groups_allowlist`
|
|
58
|
+
with `target_group_id=<root group id>`; the POST refuses a path). A new private project allows only itself, so
|
|
59
|
+
every consumer's pipeline gets 403 on the model's package although a build with a personal token resolves it.
|
|
60
|
+
Hand it to a person as a step, with the read (`GET …/groups_allowlist`) first.
|
|
55
61
|
2. Write the XSD under `schema-definition-xsd/`: single `xs:` prefix, `targetNamespace` with `xmlns:tns`,
|
|
56
62
|
`elementFormDefault="qualified"`, one root element `<Name>_vN` that references every complex type. Enumerations
|
|
57
63
|
as `xs:enumeration`. `klok datamodel validate` checks it with the pipeline's rules before you push.
|