-
Notifications
You must be signed in to change notification settings - Fork 29
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
Private harbor fix #711
Conversation
deployment/helm/skaha/desktop-template/start-software-sh.template
Outdated
Show resolved
Hide resolved
deployment/helm/skaha/desktop-template/start-software-sh.template
Outdated
Show resolved
Hide resolved
skaha/src/main/java/org/opencadc/skaha/registry/ImageRegistryAuth.java
Outdated
Show resolved
Hide resolved
skaha/src/main/java/org/opencadc/skaha/utils/CommandExecutioner.java
Outdated
Show resolved
Hide resolved
@shinybrar Could you please take a look at this PR as well? |
There was a problem hiding this 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
skaha/src/main/java/org/opencadc/skaha/registry/ImageRegistryAuth.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@at88mph @shinybrar - Does the removal of the "headless" type affect the behaviour of the API at all? |
…nto private-harbor-fix
…nto private-harbor-fix
…nto private-harbor-fix
…nto private-harbor-fix
…nto private-harbor-fix
…nto private-harbor-fix
Added ability to specify
x-skaha-registry-auth
to request header in formatbase64Encode(username:secret)
.Cleanup for Checkstyle
Added to Desktop and passed to Desktop App