Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update versions to v3.1.2 #19

Merged
merged 1 commit into from
Jul 12, 2024
Merged

Update versions to v3.1.2 #19

merged 1 commit into from
Jul 12, 2024

Conversation

amrc-benmorrow
Copy link
Contributor

No description provided.

@amrc-benmorrow amrc-benmorrow merged commit 5e70b66 into main Jul 12, 2024
@amrc-benmorrow amrc-benmorrow deleted the bmz/update-versions branch July 12, 2024 08:09
amrc-benmorrow pushed a commit that referenced this pull request Jul 25, 2024
amrc-benmorrow added a commit that referenced this pull request Jul 25, 2024
Service registration over HTTP was not correctly recording the
associated Sparkplug device. This was causing issues with clients that
need to access the change-notify interface.

More fundamentally, the service registration table was allowing a
distinction between 'the principal which registered this service' and
'the Sparkplug device associated with this service'. This was because
when the interface was designed I was trying to allow a Kerberos
principal and its associated Sparkplug Node to use different UUIDs.
Since then I have decided that this is incorrect, and the Sparkplug Node
address is simply an alternative identifier for the same principal as
the Kerberos UPN. Remove the separate `principal` table, and simply
record service registrations as owned by their Sparkplug device.
amrc-benmorrow added a commit that referenced this pull request Jul 25, 2024
Associate a Sparkplug Group with each cluster. Create a Sparkplug
Address entry giving just the `group_id`.
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