Currently, Harness provides a single Docker plugin that can be configured for:
  • Build and Push
  • Build Only
  • Push Only
This is controlled through environment variables. However, when integrating a container scanning step (e.g., Prisma), the workflow becomes cumbersome because we need to:
  • Use one Docker plugin for Build Only
  • Use a separate Docker plugin for Push Only
  • Add a third plugin for Scan
This results in multiple steps and plugins, making the pipeline less intuitive and harder to manage visually.
Feature Request:
Introduce a unified Docker plugin that supports:
  • Build
  • Scan
  • Push
…all within a single plugin configuration via the Harness UI (Visual View). This would allow users to:
  • Configure scanning tools (like Prisma) directly within the same plugin.
  • Reduce pipeline complexity and improve maintainability.
  • Provide a more streamlined experience for container lifecycle management.
Why This Matters:
  • Simplifies pipeline design.
  • Reduces the number of plugins and steps required.
  • Improves usability for teams adopting container security best practices.