title: Remote repository for a go project in Artifactory doesn't proxy?
body: <p>I'm trying to understand how to work with a remote repository in Artifactory for a Go project. My initial expectation was that it'll work transparently,  all I would need to do is to point <code>GORPOXY</code> variable to a virtual repository (with local and remote behind it), do <code>go build</code> and dependencies will either be downloaded from the Artifactory cache or Artifactory would download them transparently. Similar to the way it works for maven dependencies.</p>
  
  <p>When I tried that, it complained that the dependencies weren't found in artifactory. Ok.</p>
  
  <p>Reading <a href="https://jfrog.com/blog/goproxy-artifactory-go-registries/" rel="nofollow noreferrer">the documentation</a> two things stand out. First, there's nothing there about <code>GOPROXY</code> and everything is about using artifactory cli. That's a big downside for several reasons.
  Second, is that you need to publish dependencies manually with <code>jfrog rt go-publish go --self=false --deps=ALL</code> and then dependencies appear under a local repository. </p>
  
  <p>So I'm trying to figure out if 1) I can avoid using JFrog CLI and 2) what's the point of remote repositories if they don't proxy? Or maybe I'm missing something?</p>
  
  <p>Artifactory 6.3.0</p>