K8S / AWS Dependency Management
B
Beryl Mandrill
We would like to request consideration for enhanced dependency identification capabilities within the deployment process.
While we acknowledge that Harness currently provides an artifacts page for manual artifact specification, we have identified that this approach does not comprehensively address all use cases. For example, in Kubernetes deployments, container images may be hardcoded directly within manifest files, bypassing the standard artifact declaration workflow.
Proposed Enhancement:
We would appreciate the implementation of an automated pre-deployment scanning mechanism that would:
- Systematically identify all artifacts and dependencies referenced within deployment configurations
- Detect hardcoded references (e.g., container images embedded in Kubernetes manifests)
- Automatically catalog these artifacts and make them available as trackable entities during pipeline execution
This capability would significantly improve deployment visibility, governance, and artifact management across our CI/CD workflows.
Log In