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
I am trying to clone a directory/package from a private git repo which has been registered. While executing the clone command, I am getting the below authentication issue.
$ kpt alpha repo get -A
NAME TYPE CONTENT DEPLOYMENT READY ADDRESS
test-catalogue git Package false True https://github.com/******/***********.git
Since it is a private repository, I have hidden some details above with *
Note:
kpt alpha rpkg init/push/propose is working correctly with the above repository. Hence, I doubt if the credentials are an issue.
Expected behaviour.
If I have passed the repository details to the clone command --repository=test-catalogue, then authentication should have been addressed by the secretRef in the Repository CR.
The text was updated successfully, but these errors were encountered:
So Porch doesn't currently have support for doing git or oci-based clones from private repositories. We are open to contributions here, but it should probably start with a design proposal, as it is not obvious how it would work.
But if the repository you want to clone from is either a Porch repository, or has a structure that allows you to register it with Porch, you can do a clone where you reference the Kubernetes name of the PackageRevision rather than the git repository. This is the "package" option described in the documentation.
I am trying to clone a directory/package from a private git repo which has been registered. While executing the clone command, I am getting the below authentication issue.
Repo registration details
Since it is a private repository, I have hidden some details above with
*
Note:
kpt alpha rpkg init/push/propose
is working correctly with the above repository. Hence, I doubt if the credentials are an issue.Expected behaviour.
--repository=test-catalogue
, then authentication should have been addressed by thesecretRef
in the Repository CR.The text was updated successfully, but these errors were encountered: