Accept rubygems and go registries in the repository config

Stack, in merge order:

  1. updater !208
  2. orchestrator !67
  3. orchestrator !68
  4. orchestrator !62
  5. gitlab !256224 (merged)
  6. gitlab !264336 (merged)
  7. gitlab !264337 (this MR)
  8. docs !256327
Merge notes
  • Different repositories can merge in parallel. Within a repository, keep the order above.
  • Tag an updater release after !208 and an orchestrator release after !62.
  • Keep dependency_management_registry_credentials off. Nothing is active in production until it is on and the proxy is enabled.
  • Merge the docs last, after !264336 (merged), the orchestrator release and enabling the proxy.

Third of three stacked merge requests for #624431, on top of !264336 (merged).

Adds the rubygems and go kinds to .gitlab/dependency_management.yml, mapped onto dependabot's rubygems_server and goproxy_server credentials.

  • rubygems_server is sent with the full url. The proxy then matches host, port and path prefix, so the token only reaches that registry, even when an npm or python registry shares its host.
  • replaces-base is rejected for rubygems. dependabot only reads it to build gem metadata links from the credential's host, which is not set.
  • goproxy_server takes the username/password pair, so a go registry must set a username, the same as maven.

The updater passes credentials to the go_modules file parser, which is where GOPROXY is set from the goproxy_server credential (gitlab-org/security-products/dependency-management/updater!208).

Edited by Albina Yusupova

Merge request reports

Loading
Loading