Conversation
Signed-off-by: Vishnu Challa <vchalla@vchalla-thinkpadp1gen2.rmtusnc.csb>
| "target_hit_size": env_config["target_hit_size"] | ||
| } | ||
|
|
||
| if ('push_pull' in phases_list): |
There was a problem hiding this comment.
Is it possible to split this further into separate push/pull tests? For things like the registry proxy only pulls are supported. If not, would we be able to run the push_pull test against the registry proxy and expect to see all image pushes failing?
There was a problem hiding this comment.
would we be able to run the push_pull test against the registry proxy and expect to see all image pushes failing?
Yes
| "uuid": env_config["test_uuid"], | ||
| "auth_token": env_config["auth_token"], | ||
| "batch_size": env_config["batch_size"], | ||
| "tags": tags, |
There was a problem hiding this comment.
Could we pass in a set of tags to pull explicitly via environment variables? i.e. have something like TAGS="registry.stage.redhat.io/ubi9/ubi,registry.stage.redhat.io/ubi9/podman". It looks like the tags are based on what the tests can push to quay, but for the registry proxy it won't be able to push any images
There was a problem hiding this comment.
This ask seems very specific to proxy. I would say, use this PR to upload images without proxy and then pull them using a custom loop script (which should be pretty simple to write) by enabling the proxy if that makes sense
adding skip_push option and tags option
Description
Adding push/pull phase to only test push pull which a given user login details. This will be helpful to test both quay.io and quay-operator as well
Testing
Tested and verified by testing it on quay.io staging environment details shared by @SeanZhao-redhat
Input ENVs in the config
Output logs