Skip to content

Add Schema_UUID and Instance_UUID tags for all nested objects in edge agent config #504

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

Merged
merged 2 commits into from
May 7, 2025

Conversation

AlexGodbehere
Copy link
Contributor

This commit fixes an issue where Schema_UUID and Instance_UUID entries for nested objects in the originMap were not being consistently included in the generated edge agent configuration.

Changes:

  • Modified processOriginMapObject in edgeAgentConfigUpdater.js to add Instance_UUID tags for metric objects (with Sparkplug_Type)
  • Added handling for both Schema_UUID and Instance_UUID in non-metric nested objects
  • Ensures all levels of the originMap hierarchy properly include both Schema_UUID and Instance_UUID in the generated configuration

This ensures that device configurations correctly maintain object identity and type information through both Schema_UUID and Instance_UUID at all levels of nesting, not just at the root level.

… agent config

This commit fixes an issue where Schema_UUID and Instance_UUID entries for nested
objects in the originMap were not being consistently included in the generated
edge agent configuration.

Changes:
- Modified processOriginMapObject in edgeAgentConfigUpdater.js to add Instance_UUID
  tags for metric objects (with Sparkplug_Type)
- Added handling for both Schema_UUID and Instance_UUID in non-metric nested objects
- Ensures all levels of the originMap hierarchy properly include both Schema_UUID
  and Instance_UUID in the generated configuration

This ensures that device configurations correctly maintain object identity and type
information through both Schema_UUID and Instance_UUID at all levels of nesting,
not just at the root level.
… in edge agent config

This commit fixes an issue where Schema_UUID and Instance_UUID entries for nested
objects in the originMap were not being included in the generated edge agent configuration.

Changes:
- Refactored processOriginMapObject in edgeAgentConfigUpdater.js to process Schema_UUID
  and Instance_UUID at the beginning of the function for all object levels
- Ensures all levels of the originMap hierarchy properly include both Schema_UUID
  and Instance_UUID in the generated configuration
- Removed duplicate code that was handling these UUIDs inconsistently

This ensures that device configurations correctly maintain object identity and type
information through both Schema_UUID and Instance_UUID at all levels of nesting,
not just at the root level.
@AlexGodbehere AlexGodbehere merged commit 6f121b2 into main May 7, 2025
1 check passed
@AlexGodbehere AlexGodbehere deleted the ago/fix-missing-object-uuids branch May 7, 2025 10:25
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