Skip to content

Rollout FF packages_dependency_proxy_pass_token_to_policy

What does this MR do and why?

This rolls out the feature flag packages_dependency_proxy_pass_token_to_policy, a derisk-type feature flag introduced in !149977 (merged).

Rollout issue: #441588

The feature flag has already been enabled in production.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

No UI changes 🌈

How to set up and validate locally

There should be no behavior changes. Dependency Proxy should work just like before with personal access tokens (human user and service account user), group access tokens, and group deploy tokens.

Test the following for:

  • human user personal access token
  • service account personal access token
  • group access token, and
  • group deploy token
docker logout http://gdk.test:3000
docker login gdk.test:3000 -p <token>
docker pull gdk.test:3000/flightjs/dependency_proxy/containers/alpine:latest

# Note down the Image ID of alpine:latest
docker images
# Delete alpine:latest so we can pull it again
docker rmi <image-id-of-alpine-latest>

Related to #434291

Edited by Radamanthus Batnag

Merge request reports