You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 26, 2021. It is now read-only.
Similar to goharbor/harbor#3117, everyone from the Developer role upwards should be able to download the certificates and the env files for their VCHs from the Management Portal. At the moment, in the docs we have to tell developers to ask their vSphere admin for these files, which isn't very high-tech.
I searched the open issues for something similar but didn't see anyway. Sorry if this is a dup.
The text was updated successfully, but these errors were encountered:
The screenshots (shown in goharbor/harbor#3117) are coming from harbor UI and once that issue (3117) is resolved they'll be shown in admiral (eventually an increment of the harbor ui component version may be needed - depending on how harbor team fixes the issue - in the current version or producing a new one).
@lazaringoharbor/harbor#3117 is talking about the Registry certificate only. What I am talking about is making the VCH certificates, and ideally the VCH env file available in the UI too. Since you add VCHs in Admiral, my assumption was that it would Admiral's job to make the certs/env file available.
stuclem
changed the title
Provide a means for developers for download VCH certs and env file from UI
Provide a means for developers to download VCH certs and env file from UI
Sep 15, 2017
I would like to see some means for this as well. It seems a bit fragmented to let Devs log into Admiral with SSO, then have to arrange for some other means to get them certificates for VCH access.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to goharbor/harbor#3117, everyone from the Developer role upwards should be able to download the certificates and the
env
files for their VCHs from the Management Portal. At the moment, in the docs we have to tell developers to ask their vSphere admin for these files, which isn't very high-tech.I searched the open issues for something similar but didn't see anyway. Sorry if this is a dup.
The text was updated successfully, but these errors were encountered: