Skip to content

docs: [AH-1526]: Clarify upstream proxy naming convention #10875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions docs/artifact-registry/ar-best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,12 +81,11 @@ Use upstream proxies at **account or org level** to:
The upstream proxy is essential for caching open-source dependencies. During a build, if a required dependency is not already cached, it is retrieved from a public repository and stored in the Upstream Proxy artifact tab. This ensures continuous availability, even if the source repository (e.g. Docker Hub or Maven Central) experiences downtime. Harness’s caching mechanism enhances reliability and efficiency by reducing dependency on external services and safeguarding access to critical artifacts.
:::

### Examples
- `acct-proxy-dockerhub`
- `acct-proxy-npmjs`
- `org-proxy-private-registry`

---
### Proxy registry name guidance
- For account-wide proxies, a team name is **not** required in the registry name.
- Including `proxy` in the registry name (e.g., `acct-docker-proxy-dev`) is helpful for clarity and governance.
- You do **not** need a separate proxy for each environment.
- Example: `acct-docker-proxy-dev`

## Governance and ownership
Define roles and responsibilities:
Expand Down