Skip to content

fix: new user-domain-changed event format#626

Open
DavidePrincipi wants to merge 1 commit intomainfrom
bug-7747
Open

fix: new user-domain-changed event format#626
DavidePrincipi wants to merge 1 commit intomainfrom
bug-7747

Conversation

@DavidePrincipi
Copy link
Member

From Core 3.16+ the event carries multiple domains in a single event. Check if our user domain is in the event "domains" list.

The old "domain" attribute is still present in the event payload for backward compatibility.

Refs NethServer/dev#7747
Wants NethServer/ns8-core#997 NethServer/ns8-ldapproxy#24

From Core 3.16+ the event carries multiple domains in a single event.
Check if our user domain is in the event "domains" list.
@github-actions
Copy link

github-actions bot commented Dec 9, 2025

ℹ️ API content change detected:

No structural change, nothing to display.

Preview documentation

Powered by Bump.sh

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request updates the event handler to support the new event format introduced in Core 3.16+, where the user-domain-changed event can carry multiple domains in a single event payload using a domains list instead of a single domain field.

  • Updated the event handler logic to check if the user domain is in the event's domains list
  • Updated minimum core version requirement to 3.16.0-0
  • Improved consistency by extracting USER_DOMAIN into a variable

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
imageroot/events/user-domain-changed/20configure_ldap Updated to handle new multi-domain event format by checking if the user domain is in the domains list
Containerfile Bumped minimum core version to 3.16.0-0 to reflect new event format requirements

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants