Skip to content

limits.md

Latest commit

 

History

History
35 lines (34 loc) · 2.95 KB

limits.md

File metadata and controls

35 lines (34 loc) · 2.95 KB
Raw

Known limits

  • The structured policy editor covers DirXML Script. XSLT and ECMAScript are edited as source.
  • The editor's grammar table (web/src/policy/grammar.json) is generated from the DirXML Script DTD that ships with Designer by tools/dtd2grammar.py; regenerate it for a newer DTD.
  • The PRD and form editors cover the common settings; an activity's REST, role-request, resource-request and notification settings, a form field's other properties and owners, approvers and other languages of a role go through Operations (flow.activity.set, form.field.set --prop, role.set). Branches are inserted with flow.branch.add there.
  • package.import (a jar from disk) is CLI-only — Update sites covers repositories.
  • Deploy from the page covers deploys, the secrets mode (none / missing / all), a first deploy with missing secrets, deleting a driver the diff reports as only in the vault, and rollback to any of the environment's snapshots, and drift capture. The interactive step-by-step deploy (--step, a question per change) stays with idm vault.deploy; the page's way to deploy in parts is the scope selector, one driver at a time.
  • Update this branch from … writes files only. A driver's empty policy folder (publisher/, subscriber/) that idm import-live creates is not made, since git does not keep empty folders. A partial pull rewrites only the named drivers' folders and the set's manifest. Ticking files picks among those the review listed, and within a file the merge is line by line; a deleted file is taken or left whole. A deploy always takes the whole scope (a driver or the set): the vault matches a commit, never part of one.
  • The trace view reads over the environment's LDAPS connection. It keeps the last 50,000 records and shows the last 15,000 by default; both can be changed in its settings. Longer captures go to a file (record to a file), opened from Trace files.
  • The simulator view creates plain cases (a driver, a channel, an input document). A case's other keys (schema, a fake directory, assertions, a live query source) are honoured when run but are edited in its files; comparing with another tree stays with idm simulate --against.
  • Cases are kept in cases/ beside the tree (or --cases DIR). They are not part of the tree's revision: the page reloads them after its own writes.
  • Pull requests are created through the API on a hosted server (the person's own provider token, else the project's; the local container is one), and through gh or glab on a workstation install (serve <tree>), signed in already. A remote on another provider, a project without a token, or a workstation without a signed-in CLI gets the compare-page link. Reviewers, labels and merging stay on the provider.
  • Exporting a project uploads and downloads it whole (up to 512 MB zipped). A project written new mints fresh Designer ids, so two exports of the same tree differ in their ids, as with the CLI.