Repository navigation
Releases: PointBlueTechnology/DirXMLDevWeb
Releases · PointBlueTechnology/DirXMLDevWeb
Release list
DirXMLDevWeb 0.88.0
Needs DirXMLDev 0.65.0.
Fixed
- A GCV tested in a policy condition but defined nowhere no longer fails validation (DirXMLDev 0.65.0).
The engine reads an undefined GCV in an<if-global-variable>condition as having no value, so nothing
fails. Anavailable/not-availabletest is no longer reported, and any other test is the info
gcv-undefined-condition. This no longer blocks Plan and Deploy. A GCV that a policy substitutes is
still an error.
DirXMLDevWeb 0.87.0
Needs DirXMLDev 0.64.0.
Added
- Trace size limits in deploys (DirXMLDev 0.64.0). The tree now records each driver's trace size
limit, and a new driver is created with it and with the trace level and file the tree saw. On the
Deploy step, write the tree's trace size limits over the vault's also writes the limit on existing
drivers. Without it the vault keeps its own and the plan notes the difference. It never restarts a
driver, and a limit difference never stops a production deploy as drift. The agent toolsplan_deploy
anddeploytaketraceSizeLimit.
DirXMLDevWeb 0.86.0
Needs DirXMLDev 0.63.0.
Fixed
- A deploy no longer rewrites package stamps it doesn't change (DirXMLDev 0.63.0). Changing a
packaged object, such as one value in a GCV object a package installed, planned the
DirXML-PkgItemAuxclass and all three package stamps again with the values the vault already held,
so a one-value change showed five steps. The plan now writes only the stamps that differ. - Cache sizes say they are bytes. The Drivers tab, the engine counters, a driver's status and the
Architecture view's tooltip showed a driver's cache as a bare number, such as465. That reads as 465
queued events, but the engine reports the size in bytes; 465 bytes was two events. They now read
465 bytes. view beside the size still lists and counts the events.
0.85.0
Needs DirXMLDev 0.62.0.
Added
- Remote Loader drivers' driver object password (DirXMLDev 0.62.0). A secrets file can hold
<driver>.driver-object-password, the password the Remote Loader signs in to the engine with,
and a deploy sets it on the driver object. A new Remote Loader driver needs it, as it needs
<driver>.remote-loader-password.
Fixed
- Remote Loader drivers set up the usual way are recognised (DirXMLDev 0.62.0). A driver whose
auth server isREMOTE(hostname=… port=…)…, as Designer writes it for a native shim such as
AD's, now counts as a Remote Loader driver. Before, a deploy never set its Remote Loader password.
Upgrading: a deploy that creates such a driver now needs both passwords in the secrets file,
or it is refused. - A deploy of chosen drivers keeps to their secrets (DirXMLDev 0.62.0). With the secrets set
to missing or all, it no longer plans, or refuses over, other drivers' secrets.
0.84.0
Needs DirXMLDev 0.61.0.
Fixed
- A driver's shim password set by a deploy now works (DirXMLDev 0.61.0). Before, a deploy that
set<driver>.shim-auth-passwordwrote it to the vault in clear text. The shim then connected
with no DN and no password, and the engine refused to change that password afterwards (-638).
The password is now set through the engine, as Designer and iManager do it. When it meets a
clear-text value left by an earlier version, it removes it and sets the password again, and the
deploy's notes say so. Upgrading: set the shim password once more, with a deploy or in
Designer or iManager, on every driver where an earlier version set it.
Changed
- The hosted install says how to cap the server's memory on a shared host (#179).
0.83.0
Needs DirXMLDev 0.59.0.
Fixed
- A large project no longer runs the server out of memory on the schema and provisioning pages
(#177). Each of their requests read and parsed the whole tree again, and a page sends several at
once. They now read the tree the outline keeps, read again only when its files change. - The warning that
hosted.properties"is readable by other users" no longer shows on a folder
that ignoreschmod, such as a Windows folder mounted into the container, where its advice
can't be followed (DirXMLDev 0.59.0).
Changed
- The server may use three quarters of the container's memory (
-XX:MaxRAMPercentage=75); Java's
default is a quarter.IDM_JAVA_OPTSinidmweb.envstill overrides it (-Xmx4g). The first
log line says how much it has (heap up to … MB), and the quickstart and hosted install say
what to do when the log showsOutOfMemoryError.
0.82.0
Needs DirXMLDev 0.58.0.
Added
-
Library objects that live in another Library of the vault (DirXMLDev #111) are marked
read-only:- Outline and Developer view: a badge, with the Library's DN on hover.
- The object's page: the source only. There's no Rename, Delete or structured editor, and a
note says where the object lives.
Links to it keep its DN, compare and deploy leave it alone, and the core refuses an edit to it.
Changed
- Pins DirXMLDev 0.58.0:
vault.deploy-schema --yesis behind the agent write gate;- the
idmCLI in the image refuses arguments a command doesn't take, and a flag no longer
takes the next word; driver.queryis gated, anddriver.migrate --dry-runisn't.
0.81.0
Needs DirXMLDev 0.57.0.
Fixed
- Importing a Designer project that holds two objects of one name (a driver set using Libraries in
two containers, or a package upgrade's leftover) no longer gives a project where nearly every
page fails withduplicate artifact path(#174). The import keeps one, and the page now waits
on the result, saying which one it kept and what was left out, until you open the workbench. The
first commit's message records it too. A project imported before this loads again, and
validation names the duplicate.
Changed
- "An internal error" says where the server log is (
docker logs idmweb, or the terminal that
runs the server); the quickstart's Day to day says so too.
0.80.0
Needs DirXMLDev 0.56.0.
Added
-
The GCV tab on a driver set served by several servers (#134). Each server holds its own copy of a
driver's GCVs, and the tab showed the primary's without saying so. Now:- the Value column is headed Value on (primary), and a note above the table names the
servers that follow it; - each of the driver's own GCVs has a field per other server, outlined where that server holds a
value of its own and not defined where its copy lacks the GCV. Typing sets that server's value
(gcv.set --server, through the review); emptying it puts the primary's back; - a GCV only another server defines is listed, not defined on , with no delete button.
GCVs from a resource or the driver set are the same on every server and have no server fields.
- the Value column is headed Value on (primary), and a note above the table names the
Changed
- README screenshots retaken on the current page, from one lab driver set; the GCV shot shows the per-server field.
DirXMLDevWeb 0.79.0
Needs DirXMLDev 0.55.0.
Added
- Compare projects: pairing on the page. Pair with … proposes the map (look-alike
drivers, the nearest-named servers) or shows the pair's file, compares with it as you edit it,
and lets you leave differences pending or accept them as known. Then it writes the map (as
written), the first record and the known differences into a new branch,promote/<project>-pair-<time>,
committed and pushed for review.GET /api/promote/map,POST /api/promote/pair,
GET /api/promote/compare?map=. - Known differences on the page: accept a difference as known (intended, or to decide later),
or a known one as no longer known. The decisions go with the next promotion, or alone in a
branch of their own (known,forgetonPOST /api/promote/apply). - Cases move with their driver: when both projects have simulator cases, their files compare
and promote ascases/<path>, withdriver=written as this project names the driver. - Agents: MCP
compare_projects(each difference with its bucket and changed lines) and
promote_changes(dry run by default; the branch otherwise).GET /api/promote/compare?brief=true,
dryRunonPOST /api/promote/apply. - Docs: compare-projects.md (pairing, known differences, cases, agents, a first time
through), agents.md (the two tools), the tutorial's next steps. git-workflow.md opens with the
two ways to keep environments side by side, and when to choose which. features.md lists
Compare projects.