Default Slack Notification Template contains a misplaced comma in the JSON Payload

[jeanbritz]

Current Behavior

Currently the Slack notifications for BOM_CUNSUMED and BOM_PROCESSED and maybe other types of notifications are not delivered successfully to Slack, due to malformed JSON sent by Dependency Track.

See example JSON payload:

{
    "blocks": [{
            "type": "header",
            "text": {
                "type": "plain_text",
                "text": "BOM_CONSUMED"
            }
        }, {
            "type": "context",
            "elements": [{
                    "text": "*INFORMATIONAL*  |  *PORTFOLIO*",
                    "type": "mrkdwn"
                }
            ]
        }, {
            "type": "divider"
        }, {
            "type": "section",
            "text": {
                "text": "Bill of Materials Consumed",
                "type": "plain_text"
            },
        }, {
            "type": "section",
            "text": {
                "text": "A CycloneDX BOM was consumed and will be processed",
                "type": "plain_text"
            }
        }
    ]
}

This is due to a misplaced comma in the Pebble template file for slack notifications. See here

Steps to Reproduce

Prerequisites:

• Setup simple HTTP server which parses JSON for any incoming requests.

1. Setup Slack notification within Dependency Track with the destination URL set to point to the simple HTTP server.
2. Upload SBOM to Dependency Track and wait for notification to fire.
3. If Slack notification has been setted up correctly, you would receive an error in your HTTP server, which points to the misplaced comma

Expected Behavior

Pebble notification for Slack should be revised and checked to contain valid templated JSON. If this is done, all types of notifications should be delivered successfully to the designated Slack channel.

See screenshot below on how the end result should look like:

Dependency-Track Version

4.9.0

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

12

Browser

Google Chrome

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this defect was already reported

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.