CI Maintenance: Removed Post-Build Webhook Notification from Frontend Docker Build Pipeline

An internal build-pipeline cleanup removed an automated webhook notification that fired after each frontend Docker image was built and pushed to the container registry. This is a CI/CD maintenance change with no effect on the DSM application, its features, or end users.

The frontend's Docker-to-ECR build workflow ended with a step that POSTed a notification to an external webhook endpoint after every successful image build and push. This step was being retired — likely because the downstream deployment/notification mechanism it triggered is no longer used or has been replaced — so the call was removed to keep the build pipeline clean and avoid maintaining an obsolete, unused integration.

No user-facing or client-facing impact. The change affects only how the engineering team's automated build pipeline behaves: after building and pushing the frontend container image, the pipeline no longer sends an outbound webhook notification. Image building and pushing to the registry continue to work exactly as before.

• Single file changed: .github/workflows/docker-ecr.yml (GitHub Actions CI workflow), 11 lines removed, none added.
• Deleted the Send webhook notification step, which ran a curl -X POST to ${WEBHOOK_URL}/webhook with a Bearer token, reporting the built image name/tag, app name (frontend), and Git branch.
• No application source code, dependencies, infrastructure provisioning, or runtime behavior was touched.

Low risk. The change is confined to a CI workflow and only removes an outbound notification; it does not alter image building or pushing. The main consideration is that any external system relying on that webhook (e.g. an auto-deploy trigger or build dashboard) will no longer be notified — this should be confirmed as intended/decommissioned. Mitigation: the step can be restored by reverting this single, isolated change if a dependent consumer is later found.

• Trigger the frontend Docker ECR workflow and confirm it completes successfully, building and pushing the image to the container registry as before.
• Verify the Send webhook notification step no longer appears in the workflow run logs.
• Confirm no downstream system (deployment automation, monitoring, or notification consumer) was depending on the removed webhook; if one was, ensure an alternative path exists.