Support Cross-Project Repositories in Direct Push Step
H
Historic Mole
Description
The Direct Push step currently supports pushing to repositories within the same Harness project where the pipeline is executing.
It would be useful to extend Direct Push to support repositories located in other Harness projects, provided the executing identity has the required permissions to access the target repository.
This would allow pipelines and templates to be centrally managed and reused across projects without requiring the Direct Push step and target repository to exist within the same project.
Requested Enhancement
Allow the Direct Push step to:
- Select or reference a repository from another Harness project.
- Specify the appropriate organization/project scope for the target repository.
- Use the executing identity’s RBAC permissions to authorize access to the target project/repository.
This would make Direct Push more reusable for centralized pipelines and templates that operate across multiple Harness projects.
Log In