Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private harbor fix #711

Merged
merged 23 commits into from
Nov 8, 2024
Merged

Private harbor fix #711

merged 23 commits into from
Nov 8, 2024

Conversation

at88mph
Copy link
Member

@at88mph at88mph commented Oct 11, 2024

Added ability to specify x-skaha-registry-auth to request header in format base64Encode(username:secret).
Cleanup for Checkstyle
Added to Desktop and passed to Desktop App

@brianmajor
Copy link
Member

@shinybrar Could you please take a look at this PR as well?

Copy link
Collaborator

@shinybrar shinybrar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep in mind,

  • I have no Java Background
  • These are big classes of code to get lost in

Comments

  • We could use StandardCharsets.UTF_8 explicitly when converting between byte arrays and strings for encoding and decoding.
  • There is one edgecase which still goes unchecked when the user provides a valid registry server, valid registry credentials, but malformed image/tag names for private images. This will lead to a 200 for the user, but the job will fail to launch. After discussions with @at88mph -- this is a known edgecase, which is currently bound by the limitation of our system.
  • Since we perform kubectl bash command underneath the hood, the sting stream created in CommandExecutioner can create an escape scenario, if the client secret has a escape character in the secret.
  • We should add unittests for the new code added

shinybrar
shinybrar previously approved these changes Oct 16, 2024
Copy link
Collaborator

@shinybrar shinybrar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@brianmajor
Copy link
Member

@at88mph @shinybrar - Does the removal of the "headless" type affect the behaviour of the API at all?

@at88mph at88mph marked this pull request as ready for review October 18, 2024 19:53
@at88mph at88mph merged commit 645b475 into opencadc:main Nov 8, 2024
2 checks passed
@at88mph at88mph deleted the private-harbor-fix branch November 8, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants