Repository navigation
Add e2e test for authorized pull/push #5965
Description
Activity
Can I start working on it?
Hey @Benehiko,
I'm interested in working on this issue. Is it still available for contributions? Let me know if I can get assigned to it!
Thanks!
Reacted by Alano TerblancheYes, feel free to open a PR
Reacted by Aryan SharmaHello @vvoland and @AryanSharma9917,
I noticed that PR #6194 has been inactive for a few months. If the original author is no longer working on this, I would love to take over the issue and give it a try.
I am a college student studying computer science and new to open-source contributions. I am also currently learning the Go language. Would it be okay for someone like me to take over this issue?
If you give me permission, I will do my best to learn and contribute! I have great respect for you all and aspire to be a great engineer like you.
(P.S. Since English is not my first language, I used a translation tool and AI. Please bear with me if the sentences sound a bit awkward!)
Thanks @vvoland — I'll carry #6940 forward via #7007.
The CI failures look caused by a bad htpasswd volume path in
e2e/compose-env.yaml(paths are resolved relative to the compose file, so./e2e/testdata/...never mounted). I'm reopening #7007 with that fix plus a small compose cleanup (privateregistryservice name,depends_on).- added 9 commits that reference this issue
on May 26, 2026 Hey, just following up on the PR I raised. I noticed that no reviewer has been assigned yet, and I wanted to check in to make sure it doesn't go stale. Would someone be able to take a look when they get a chance? Thanks!
Description
We need an e2e test that verifies that docker pull/push works for private repositories.
This would serve as an regression test for: #5963