Send back job id to udm

[nmgaston]

The PR review is to check for sustainability and correctness. Sustainability is actually more business critical as correctness is largely tested into the code over time. Its useful to keep in mind that SW often outlives the HW it was written for and engineers move from job to job so it is critical that code developed for Intel be supportable across many years. It is up to the submitter and reviewer to look at the code from a perspective of what if we have to debug this 3 years from now after the author is no longer available and defect databases have been lost. Yes, that happens all the time when we are working with time scales of more than 2 years. When reviewing your code it is important to look at it from this perspective.

Author Mandatory (to be filled by PR Author/Submitter)

• Developer who submits the Pull Request for merge is required to mark the checklist below as applicable for the PR changes submitted.
• Those checklist items which are not marked are considered as not applicable for the PR change.
• Items marked with an asterisk suffix are mandatory items to check and if not marked will be treated as non-compliant pull requests by the developers for Inner Source Development Model (ISDM) compliance

PULL DESCRIPTION

• Modified DB to store immediate jobs to track the job ID when sending the result.
• Adding a new manageability/update channel between Dispatcher and CloudAdapter to send node updates back to INBS
• Sending the update response back to INBS via gRPC

REFERENCES

Reference URL for issue tracking (JIRA/HSD/Github): <URL to be filled>

• Added label to the Pull Request following the template: ISDM_<Complexity>*
  Note-1: Depending on complexity of code changes, use the suitable word for complexity: Low/Medium/High
  Example: PR for Slim boot loader project with medium complexity can have the label as: ISDM_Medium
• Added label to the Pull Request for easier discoverability and search
• RTC or HSD number will be included in final merge. HSD must always be included if available.
• Changelogs are updated (or N/A if not customer visible)
• inbm/log_changes.txt are updated for potentially Validation-breaking log changes (or N/A if none)

CODE MAINTAINABILITY

• Commit Message meets guidelines as indicated in the URL*
  • (https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md)
• Every commit is a single defect fix and does not mix feature addition or changes*
• Added required new tests relevant to the changes
  • PR contains URL links to functional tests executed with the new tests
• Updated Documentation as relevant to the changes
• Updated Build steps/commands changes as relevant
• PR change contains code related to security
• PR introduces changes that breaks compatibility with other modules (If YES, please provide description)
• Specific instructions or information for code reviewers (If any):
• Run 'go fmt' or format-python.sh as applicable.
• New/modified methods and functions should have type annotations on signatures as applicable
• New/modified methods must have appropriate doc strings (language dependent)

APPLICATION SPECIFIC

• Does PR change default config files under /etc? If so, will application still work after an upgrade that leaves /etc alone, like a Mender upgrade?
• Is cloud UI changed? If so, are cloud definition files updated?

Maintainer Mandatory (to be filled by PR Reviewer/Approving Maintainer)

• Maintainer who approves the Pull Request for merge is required to mark the checklist below as appropriate for the PR change reviewed as key proof of attestation indicating reasons for merge.
• Those checklist items which are not marked are considered as not applicable for the PR change.
• Items marked with an asterisk suffix are mandatory items to check and if not marked will be treated as non-compliant pull requests by the maintainers for ISDM compliance.

QUALITY CHECKS

• Architectural and Design Fit
• Quality of code (At least one should be checked as applicable)*
  • Commit Message meets guidelines
  • PR changes adhere to industry practices and standards
  • Error and exception code paths implemented correctly
  • Code reviewed for domain or language specific anti-patterns
  • Code is adequately commented
  • Code copyright is correct
  • Confusing logic is explained in comments
  • Commit comment can be used to design a new test case for the changes
• Test coverage shows adequate coverage with required CI functional tests pass on all supported platforms*
• Static code scan report shows zero critical issues*
• Integration tests are passing

CODE REVIEW IMPACT

• Summary of Defects Detected in Code Review: <%P1xx,P2xx,P3xx,P4xx%>
  Note P1/P2/P3/P4 denotes severity of defects found (Showstopper/High/Medium/Low) and xx denotes number of defects found

SECURITY CHECKS

Please check if your PR fulfills the following requirements:

• Follow best practices when handling primitive data types
• Configure minimal permissions when opening pipes and ports
• Check contents within input structures are valid before use
• All forms of input validated
• Avoid inter-process race conditions
• Error and exception handling implemented
• Defend against Canonical Representation Issues - Any paths utilized?
• Follow 'secure by default' - Any configuration values added
• Fail safe - Any failure scenarios?
• Clean up temporary files - Any temporary files being used?

Code must act as a teacher for future developers

[nmgaston]

This is still having unit test problems, but I wanted to open it up for review.

[gblewis1]

self._node_update

[gblewis1]

I think this should be node_update = config.get("[maybe nodeUpdate or node_update?]")