Skip to content

Channels found by object class; duplicate-name note across Libraries (#133) - #137

Merged
jcombs-pointblue merged 1 commit into
masterfrom
channels-by-objectclass
Nov 20, 2026
Merged

jcombs-pointblue merged 1 commit into
masterfrom
channels-by-objectclass

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

For #133, from klasen's latest run of 0.74.0: every link resolves now, but two points remained.

(a) Channels found by object class. cn=pub,cn=SAP-HR-XXX and cn=pub,cn=SAP-HR-ZZZ each held a pub-ets-ps-Relationships, linked in publisher-event. They look like the drivers' publisher channels under another name; I've asked klasen to confirm the objectClass. The readers knew channels only by the names Publisher/Subscriber, so 0.74.0 put both policies into library/ and kept one: the ZZZ driver's link read XXX's policy.

  • LdifReader (so import-ldif and import-live) finds a driver's channels by object class (DirXML-Subscriber/DirXML-Publisher). A name other than the default is kept in driver meta, channel.subscriber / channel.publisher, and written to driver.xml.
  • VaultMapping.channelDn/artifactDn/pathDn/policiesValues take the driver set and use those names, and Plan passes the tree. Deploy, plan and new channels for a new driver all use the real DNs.
  • ProjectReader records a Designer channel's name the same way. ProjectWriter names a new driver's channels from it.

(c) The duplicate-name note across Libraries. klasen asked why it says "The tree has one Library" when IDM links from any number of Libraries. He's right: it's our tree's limit, not IDM's. The note now says so. When the copies differ, it says that too and names the drivers that link the copy left out, because a deploy that rewrites their links points them at the kept copy. Drivers can be named only when the reader recorded the link DNs (LDIF or vault); a Designer project gets "check the links to it".

Not in this PR: (b), giving each Library its own place in the tree, which needs a design note first.

Tests:

  • New channelsAreFoundByObjectClass: two drivers with cn=pub/cn=sub channels keep their own policies, links resolve, and artifactDn, policiesValues and channelDn give back the real DNs.
  • rdnsAreUniqueOnlyInTheirContainer checks the new note: the content differs, and it names the linking driver.
  • 1065 tests pass on a clean build.
  • End to end: the synthetic fixture with its channels renamed pub/sub gives the same tree as the original, plus the two meta entries.

🤖 Generated with Claude Code

…133)

A driver's channel objects need not be called Subscriber and Publisher (cn=sub,
cn=pub). The LDIF reader took such a channel for a container: its policies went
into library/ and two drivers' policies of one name became one. Channels are now
found by object class; the driver records their names (channel.subscriber /
channel.publisher meta, also from a Designer project), and deploy, plan and
export-project use them.

The duplicate note across Libraries now says the limit is the tree's, not IDM's,
and when the copies differ names the drivers that link the copy left out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jcombs-pointblue
jcombs-pointblue merged commit ef0adbd into master Nov 20, 2026
4 checks passed
@jcombs-pointblue
jcombs-pointblue deleted the channels-by-objectclass branch November 20, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant