Decouple Delivery Targets From Route Groups

[cfarmer-fearless]

This is an iteration on the deliver configuration schema. The goal is to decouple delivery targets from routing groups. This will improve robustness by preventing possible misconfiguration of creating multiple delivery targets with the same name. With this, we want to make sure the server fails to start if the deliver yml is misconfiguration in this way.

[fortify-pr-scan]

Fortify Scan Results

🟢 Status: ✅ Passed

Summary

• 🚨 Critical Issues: 0
• 🛑 High Issues: 0
• ⚠️ Medium Issues: 0
• 🔍 Low Issues: 0

✅ No Action Required

No vulnerabilities were identified in this scan.

Detailed Results

📂 Scanned Path(s)

upload-server

📊 Detailed Scan Results

sourceanalyzer is installed.
FPRUtility is installed.
fortifyclient is installed.
Using Fortify Source Analyzer to scan the code from upload-server. Results will be upload-server.fpr.
Printing the results using Fortify FPRUtility, FPRUtility summarizes and translate results.
Summary of all issues:

Total for all categories => 0 Issues

****************************************************
Number of critical issues:
No issues matched search query.
****************************************************
Number of high issues:
No issues matched search query.
****************************************************
Number of medium issues:
No issues matched search query.
****************************************************
Number of low issues:
No issues matched search query.
****************************************************

Details of all issues in csv format:

[fortify-pr-scan]

Fortify Scan Results

🟢 Status: ✅ Passed

Summary

• 🚨 Critical Issues: 0
• 🛑 High Issues: 0
• ⚠️ Medium Issues: 0
• 🔍 Low Issues: 0

✅ No Action Required

No vulnerabilities were identified in this scan.

Detailed Results

📂 Scanned Path(s)

upload-server

📊 Detailed Scan Results

sourceanalyzer is installed.
FPRUtility is installed.
fortifyclient is installed.
Using Fortify Source Analyzer to scan the code from upload-server. Results will be upload-server.fpr.
Printing the results using Fortify FPRUtility, FPRUtility summarizes and translate results.
Summary of all issues:

Total for all categories => 0 Issues

****************************************************
Number of critical issues:
No issues matched search query.
****************************************************
Number of high issues:
No issues matched search query.
****************************************************
Number of medium issues:
No issues matched search query.
****************************************************
Number of low issues:
No issues matched search query.
****************************************************

Details of all issues in csv format:

[whytheplatypus]

any concerns with reducing this down to delivery.GetTarget(e.DestinationTarget)?