ROX-12037: Support Quay Robot Accounts for registry integration#2578
ROX-12037: Support Quay Robot Accounts for registry integration#2578
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
|
Images are ready for the commit at 57decb5. To use with deploy scripts, first |
9be3b70 to
62f53ce
Compare
|
/test images push-images |
|
/test stackrox_branding-images stackrox_branding-push-images |
62f53ce to
ca47b95
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images |
ca47b95 to
26e894b
Compare
26e894b to
2c0aaee
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images |
3ceb13c to
481eee7
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images |
481eee7 to
6665662
Compare
6665662 to
7eee886
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests |
7eee886 to
e0413e8
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests |
e0413e8 to
d669434
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests |
d669434 to
a4bf56a
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests |
a4bf56a to
a5ed9be
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests |
a5ed9be to
57c1542
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests go-unit-tests style-checks |
e67b841 to
bdefd5f
Compare
|
/test images push-images stackrox_branding-images stackrox_branding-push-images gke-qa-e2e-tests gke-postgres-qa-e2e-tests go-unit-tests style-checks |
2a73264 to
4b4eb71
Compare
|
/retest |
1 similar comment
|
/retest |
4b4eb71 to
2f4e9a6
Compare
cb1bece to
9bceffc
Compare
9bceffc to
5290b88
Compare
pedrottimark
left a comment
There was a problem hiding this comment.
Solid from frontend viewpoint.
Thank you for clear comments in code and example requests in description.
RTann
left a comment
There was a problem hiding this comment.
mostly nits otherwise LGTM
| if quay.GetRegistryRobotCredentials() != nil && quay.GetOauthToken() != "" { | ||
| return errors.New("Quay registry integration should use robot credentials or robot credentials but not both") | ||
| } | ||
| } else { |
There was a problem hiding this comment.
is it possible for len(categories) == 0 here? I think being inside this else assumes len(categories) == 2, right?
There was a problem hiding this comment.
It gets validated elsewhere
| username = config.GetRegistryRobotCredentials().GetUsername() | ||
| password = config.GetRegistryRobotCredentials().GetPassword() | ||
| } else if config.GetOauthToken() != "" { | ||
| username = oauthTokenString |
There was a problem hiding this comment.
nit: maybe just always do this check like before and just overwrite it with robot creds if provided? I think that will remove the need for these elses
There was a problem hiding this comment.
Kept it this way to make deleting the feature flag easier. Can just delete the else condition in that case.
Description
When integrating Quay registry you can now optionally use robot account instead of just OAuth tokens. In fact this is Quay's recommended integration credentials. Unfortunately scanner still requires a token.
Existing integrations should remain as-is.
Checklist
~[ ] Determined and documented upgrade steps
If any of these don't apply, please comment below.
Testing Performed
Auomated: See files
Manual:
Validated that on upgrade the existing integrations remain as is (with or without token).
Then just using the /test endpoint:
Registry:
Scanner:
Registry + Scanner:
And then by actually creating some integrations and using it: