V
Vertical Weasel
Harness currently does not provide a way to specify Cloud Provider connectors (e.g., GCP Artifact Registry, AWS ECR, Azure ACR) as base connectors for Docker build steps. The only supported option today is the Docker Registry connector.
Problem Statement
Our organization’s container builds require pulling base images from multiple cloud registries. Since Harness does not allow Cloud Provider connectors to be used as base connectors, this has become a blocker for all teams across the organization.
Impact
Organization-wide blocker for container builds and deployments.
Prevents us from using Harness native pipelines to build and deploy images.
Hinders adoption and standardization of Harness across teams.
Requested Enhancement
Enable Cloud Provider connectors (e.g., Artifact Registry, ECR, ACR) to be used as base connectors in Docker build steps. This capability is essential for enterprise adoption and for teams to continue building and deploying images securely and consistently using Harness.
It would also be hi