[KNOX-2302] Skip re-deployment of generated topology if the topology has not changed

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Component/s: Server
• Assignee: Philip Zampino
• Reporter: Philip Zampino
• Created: 18/Mar/20 14:25
• Updated: 23/Mar/20 17:50
• Resolved: 23/Mar/20 17:50

Description

Knox discovery always writes generated topologies to disk, triggering [re]deployment of that topology. It would be better to compare the generated topology against the already-deployed version (if it exists) prior to writing it to disk. If the generated version is the same as the already-deployed version, then the newly-generated topology should be discarded, so the re-deployment will be skipped.

Issue Links

• relates to: KNOX-2301 Trigger discovery for descriptors at gateway start time
• links to: Github Pull Request #297